Often developers get a limited choice on the Version Control (VC) or Software Configuration management tool they have to use when working on a project. However even when the Git (the Distributed Version Control tool) does not interface with the project tool there is value in using Git for a personal workflow. This can work as follows.
Rinse and repeat
- Fetch a copy of the working code needed to make your change
- Initialise a new Git repo in your working copy and add the code
- Now checkout a new git branch for your work
- hack hack hack test test....
- Switch to master branch
- Fetch from the project tool again.
- Add changes and commit
- Review differences, rebase or merge as required.
- Verify project tool still at same state from step 7
- Upload/ check in changes to project tool. You can use the output from git log as the basis of your commit message for the legacy tool