During the years, i wrongly used Visualstudioonline (now Azure DevOPs).
I created a project (believing that this was a repo) and then create a folder on each where i stored the various project.
Now i would like to separate these folder and create a Project for each folder.
Is there a way to migrate/move the single folder (with all its history) to new project ?
The sources are now in azure devops version control, and the new project has to be in the same version control and i don't want to create GIT repo.
From the webserver that there is import feature under the project, but the tools only convert from TFVC version to GIT and not from TFVC to TFVC.
I am in the same boat the way in which I am doing it as follows:
Create the new repo
Clone existing repo to my pc
Checkout all branches
Add new repo as a remote to my local repo
Push the repo to the new remote
Go through and clean up the repo
Yes it is painful but the way im doing it is as I'm working on the project.
The other option would be to fork the repo but I haven't found a way to server the fork link.
I am afraid there is currently no built-in function to migrate from tfvc to tfvc.
You can try using a third-party tool OpsHub Visual Studio Online Migration Utility to do this.
A contributor has successfully implemented this feature with this third-party tool.For details please refer to this case.
Hope this helps.
Related
In my previous Github repos, I was able to create a project under the repo which was specific to the repo, but now I cannot see this option for the new repos.
I can still use Project (Classic) in my previous repos.
Github now push me to create a project under my account, and link to the repo, but I want to create a project just under the repo.
In my side, the problem is that, when I try to create an "Issue", the user can see all of my projects under my account, but I don't want that.
The user should only see the related project.
Can I somehow have the previous version of the projects?
Thanks
Good Morning and Good Evening Everyone,
Is there a way to migrate or copy all history of a project in one project collection and move to another project collection?
For example:
I have a project collection called 'A' and 'B'
Project Collection 'A' has a .Net project that is called SalesApp.
The SalesApp has changesets that I want to keep and copy to project collection 'B'.
How do I copy my project plus the changesets into project collection 'B'?
Thank you in advance :)
Azure DevOps - how can you copy the history of a project from one project collection to another project collection?
I am afraid there is no such out of box way to achieve this. Since TFVC does not support migration between team projects.
You could try to import a GIT repo from other project will store the history info. So using GIT as a bridge is the only workaround here to keep history info. Sorry for any inconvenience for not make it more clearly. GIT here is just a bridge. You need first convert your TFVC repo to GIT.
Then move converted GIT to TFVC. Finally in target project, convert GIT back to TFVC. Just also use git-tfs command line. For your reference: Convert Git repository to TFVC version control
Besides, there is a 3rd tool, you can try it with OpsHub Visual Studio Online Migration Utility.
Recently, we migrated from our TFVC to git repository. I would like to decouple a few of our solutions into separate git repositories. Is it possible somehow to group these newly created repos under some kind of subfolder on AzureDevOps?
Is it possible to group git repositories into subfolders under AzureDevOps?
The answer is yes.
The most important thing before starting is to backup your current project/solutions.
I created a simple example to demonstrate how to accomplish it.
I created a repo with three solutions (Solution1, Solution2, Solution3)in it:
Add three subfolders (Subfolder1, Subfolder2, Subfolder3)in this repo via Azure devops web page:
Now, open our Visual Studio locally, connect to this repo. And move the solution1 to the subfolder1 in the file explorer:
Then, push this change to the repo:
Now, the solution1 moved to the subfolder1.
Update:
But basically my question was if there is possible to create
subfolders for some git repositories, not a subfolders inside git
repository
I think it is impossible to create subfolders for some git repositories. You need to create other repo in the project. When you have lots of repos, folders aren't your best friend. Tagging, quick-filter and search are.
Please check this thread for some details.
I recently inherited a project that used to be setup with Github for version control. However, due to lack of communication from the original developer, I'm left with code base that lives on the production. Question I have is if it's possible to recover a code repo in Github given that I have the .git folder that contains all git related files?
If there's an existing .git folder, it's probably an existing git repository. You could just follow the instructions for adding an existing project to Github and get it that way.
I use an open source project to host a site (OrchardCMS) which is available in a GIT repository via CodePlex. I have made a few customizations to the source code that are specific to my implementation and I want to keep preserved and under source control. However the challenge arises when there's a new release of the source engine.
My changes certainly won't go into the blessed repository everyone uses.
Currently I'm using two repositories. I use the CodePlex OrchardCMS repository to get the latest changes from the engine the community uses (and that I contribute some bug fixes to).
I then have my own copy which contains my changes. For this, I am using my own source control (hosted TFS from Microsoft). When an update to the core engine comes out, I XCOPY all the files from the current source to my self-maintained repository and commit them to my project.
However this seems like there should be a better option. Any opinions?
You can use git to have an alternative solution.
You can clone the git main repo and keep it updated with the new relases, and you can keep your local modifications, that aren't to be shared with anyone, on a local branch.
When a new release came out, you simply update your master branch in your git repo an then you can rebase or merge your local modications on top of it.