The git-tfs project was born as an experiment to see if I could use Git while my co-workers continued to use TFS. While I was learning about Mercurial and Git, my employer was using Team Foundation Server (TFS). This makes "what if?" experiments cheap and easy. When everything is a branch, there is a lot more focus on making merging as frictionless as possible. Every time you create a workspace, you have created a branch. One of the big advantages of a distributed version control system (DVCS) is its ability to sanely handle branches. It allowed me to keep a history of changes regardless of whether I was online, and I could synchronize my changes later.īeing able to work offline got me interested in Mercurial and Git, but being able to quickly and easily experiment was what really hooked me. This was exactly what I needed for my side projects. When I first learned about distributed version control tools (for example Mercurial or Git), I was quickly won over by the ability to version anything, anywhere, without ever needing to set up a server. I was subsequently thrilled to use Clear Case, Subversion, and TFS. So it shouldn't be a big surprise when I admit that, once upon a time, I was excited to use CVS. Keeping versions of my code and being able to reliably synchronize it between computers is something I can't do without. License & Pricing: Open Source (MIT), Free It fetches TFS commits into a git repository and lets you push your updates back to TFS. Git-tfs is an open source two-way bridge between Microsoft Team Foundation Server (TFS) and git, similar to git-svn. Git-TFS - Work with your Team (Foundation Server) with Git
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |