I first discovered Vincent Driessen’s branching model when I was investigating Git a couple of years ago. At the time I was desperate to get away from the merge issues that we were having with Subversion and was looking into both Git, and different branching models using it. Given the steep learning curve with Git we decided not to complicate things further and to stick with our old branching model; albeit with a slight change in naming convention borrowed from Vincent.
Now I’m a little more comfortable with Git it’s time to revisit our branching strategy, and use of Git overall. I’ve looked at Vincent’s branching model again, and looked at git-flow in great depth and have concluded it’s still not for us, however, the idea of codifying the workflow, and providing git extensions to aid using the workflow appealed to me immensely.
Currently we’re doing little more than branching off
master for issues, with each issue (be it a new feature, or bug fix) living in its own branch. Issues are rebased into
master when they’re done. Releases are also cut from
master and any patches (either to the release version in QA, or to the release version in live) are cut from the release branch, rebased into that and then rebased into
In order to simplify our JIRA and Fisheye/Crucible setup we also push issue branches to
origin making them visible from a central point, as well as providing a backup. These branches are considered private and not used by others.
Since we have tight control over all the branches a rebase only strategy works fine for our team, although we have had some problems caused by accidental merges. The next step is to improve the workflow and the merge/rebase strategies to survive all situations, codify these steps and then script them – something I’ve already started doing.