> It's like timesheets for your code. Not a big deal, but ever so slightly insulting that you have to deal with them.
Honestly, I'm not sure you have realized the true power of git branching.
Here is our typical workflow at work:
1. Branch master to topic/feature branch
2. Work on feature branch, push feature branch to remote
3. Push of feature branch to remote triggers a Tddium test run.
4. Deploy feature branch to a staging server for internal review.
5. Make fixes, adjustments to feature branch and push to remote, which triggers more Tddium test builds.
6. Once things are looking good, we pull --rebase master, which pulls down everyone elses changes to master.
7. Rebase the feature branch off of master, resolve any conflicts.
8. Merge feature branch into master and push.
Above, branching allowed me to:
* Save my own personal branches to a remote repo where they are backed up,
* Offload my test suite to a 3rd party,
* Allow me to deploy a feature branch to a staging server all without messing with the master branch at all.
I can also squash or rename commits on my branch easily and cherry-pick other commits from other branches without worrying about master. I can also VERY EASILY switch to other branches to work on other features and bugfixes as they arise. I normally work on 2-4 diff branches per day.
Try doing any of that in SVN and be in for fun ride...