Well, I started this topic mainly to share the experience I had with git-tfs recently with the community.
If anybody has anything else to share - it will be helpful for me as well.
Git in Visual Studio, Azure DevOps Services, and TFS is standard Git. You can use Visual Studio with third-party Git services, and you can also use third-party Git clients with TFS. To learn more, see Git and Azure Repos.
You should use Git for version control in your projects unless you have a specific need for centralized version control features in TFVC. In other words, if you have a very specific reason why you need to continue using TFVC, Microsoft would rather you didn't.
Git-tfs also needs to know the path in TFS that you want to clone. It can clone any path (other than the root), so you can clone an entire TFS project, or just one subdirectory of it. Use this command to create a Git repository in local-dir. The new clone includes the full history of $/Project/Path.
About work in environment where several developers use git-tfs simultaneously. About commit identity caveats actually: http://sparethought.wordpress.com/2011/06/16/first-git-tfs-usage-problems/
Is rebasing workflow with git-tfs possible? http://sparethought.wordpress.com/2011/06/21/gittfs-rebasing-workflow-is-it-possible/
Not specifically git-tfs but affects it too. Problems with HOME directory on Windows: http://sparethought.wordpress.com/2011/06/16/troubleshooting-gitextensions-home-directory/
Establishing central git repository to avoid redundant TFS round-trips: http://sparethought.wordpress.com/2011/07/18/how-to-establish-git-central-repository-for-working-against-tfs-with-git-tfs-bridge/
My environment for day-to-day work with git-tfs: http://sparethought.wordpress.com/2012/08/23/my-environment-for-day-to-day-work-with-git-tfs/
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With