Once the department's key players were convinced migration to git was a must, we had to get it done. The following steps were taken in order to successfully migrate our code base.
Since a team can work with various repositories hosted on the same server, the following question comes to mind : how many repositories do we create? Once again, the answer came from our CI/CD (continuous integration and continuous delivery/deployment) implementation: one repository per pipeline.
There are two new key concepts to absorb. Hasty learners who do not take the time to assimilate them will be left behind. Introducing git is not the purpose of this post. Rather, we will map git concepts to TFS concepts.
From the start of the integration of continuous integration and delivery, TFVC has not delivered in terms of branching, tagging and team collaboration. With new developers joining our team with diverse experience in using git and migrating from TFVC to git a choice needed to be made. The department decided on git and nobody misses TFVC.