We are considering migrating from TFVC to GIT (probably hosted within TFS).
Main reason is the bad support for file movement, which makes larger refactorings a pain. Merging generally is rather poor, often asking for manual resolution even if just one side of the merge has been updated. Another bad fact is that we currently have several team projects, and would like to include (via source) some shared functionality, this seems hard to do when several team projects are involved.
What would be a good organisation for the GIT repo for TFS considering
- we have multiple solutions (right now, spread over different team projects)
- we plan to have some shared code referenced in several solutions, for debugging in source format
- right now, we have many legacy feature branches and wanted to keep a main an dev branch for the major solutions (if that workflow is decent with GIT. In TFVC I noticed that the many branches clutter the source control.)
- build should work via build agent like before, also taking into account the shared project (changes there trigger a build)
- history should be preserved
We are using https://github.com/git-tfs/git-tfs for the migration so far, which seems reasonably good. We don't care much for work items or similar.
Please share your insight. After some quick research I am wondering if it would be worth it, since it seems to be some work, amongst others deciding on a repo structure as well as setting up the build projects anew.