At our company we have a very old codebase which is hosted using TFVC on Azure DevOps. The repository has grown to be +- 10GB, which would be way too big for a GIT repository. It contains a lot of redundant data which we’d be able to prune away. However, this will take some time and we don’t want to halt development during this migration process.
The old repo is roughly set up like this:
$Project
|_FolderA
|_FolderB
|_FolderC
|_FolderC_OLD
|_SomeAssetsFolder
|_Some3rdParyLibraryFolder
The folders aren’t branches. They are folders inside of the root of the project.
Our strategy to move to GIT was as following;
- Branch the project to a new project
- Prune the new project while development continues on the old projectrepo
- Once pruning and other necessary edits are done, merge the old projectRepo into the new project
- Convert the new repo to a GIT repo using Git-TFS
- Done
However, this doesn’t seem to work as intended; we can’t seem to branch the whole project, only folders inside of the project.
- Will we be able to merge the old project into the new one, even if we have to branch each folder individually?
- Is there another way to clone the complete project into a new project, allowing us to merge the changes at a later moment?
Sid is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.