With a git layer over whatever other source control system is required for the team:
- I can check-in or revert individual lines of code in a file.
- I can create a branch for local modifications that should never be checked into the team source control.
- I can create mini-commits that don't have to be logged as individual commits in the team source (for teams that prefer one large change-set)
- I can create my own personal historical record of change save-points and notes/comments
- I can select which lines of a file should go into a check-in without shelving the entire change.
Create a junction or hardlink to the folder that contains your code. This junction must not be in the tree that your tfs workspace mapping sees. If it is, Visual Studio will then, forcefully and persistently, use git as your source control and refuse to talk to TFS about your changes.
So I have all my code under
- I change working directory to
mklink /h /j foobar c:\development\foo
- Always point visual studio at the legacy folder
- Always point your git tool(s) at