date: 2020-04-06 title: My unorthodox, branchless git workflow
layout: post
I have been using git for a while, and I took the time to learn about it in great detail. Equipped with an understanding of its internals and a comfortable familiarity with tools like git rebase — and a personal, intrinsic desire to strive for minimal and lightweight solutions — I have organically developed a workflow which is, admittedly, somewhat unorthodox.
In short, I use git branches very rarely, preferring to work on my local master branch almost every time. When I want to work on multiple tasks in the same repository (i.e. often), I just… work on all of them on master. I waste no time creating a new branch, or switching to another branch to change contexts; I just start writing code and committing changes, all directly on master, intermixing different workstreams freely.^1 This reduces my startup time to zero, both for starting new tasks and revisiting old work.
When I’m ready to present some or all of my changes to upstream, I grab git rebase and reorganize all of these into their respective features, bugfixes, and so on, forming a series of carefully organized, self-contained patchsets. When I receive feedback, I just start correcting the code right away, then fixup the old commits during the rebase. Often, I’ll bring the particular patchset I’m ready to present upstream to the front of my master branch at the same time, for convenient access with git send-email.
I generally set my local master branch to track the remote master branch,^2 so
I can update my branch with git pull --rebase.^3 Because all of my
work-in-progress features are on the master branch, this allows me to quickly
address any merge conflicts with upstream for all of my ongoing work at once.
Additionally, by keeping them all on the same branch, I can be assured that my
patches are mutually applicable and that there won’t be any surprise conflicts
in feature B after feature A is merged upstream.
If I’m working on my own projects (where I can push to upstream master), I’ll
still be working on master. If I end up with a few commits queued up and I need
to review some incoming patches, I’ll just apply them to master, rebase them
behind my WIP work, and then use git push origin HEAD~5:refs/heads/master to
send them upstream, or something to that effect.^4 Bonus: this instantly
rebases my WIP work on top of the new master branch.
This workflow saves me time in several ways:
- No time spent creating new branches for new features.
- No time spent switching between branches to address feedback.
- All of my features are guaranteed to be mutually applicable to master, saving me time addressing conflicts.
- Any conflicts with upstream are addressed in all of my workstreams at once, without switching between branches or allowing any branch to get stale.
I know that lightweight branches are one of git’s flagship features, but I don’t really use them. I know it’s weird, sue me.
Sometimes I do use branches, though, when I know that a workstream is going to be a lot of work — it involves lots of large-scale refactoring, or will take several weeks to complete. This isolates it from my normal workflow on small-to-medium patches, acknowledging that the large workstream is going to be more prone to conflicts. By addressing these separately, I don’t waste my time fixing up the error-prone branch all the time while I’m working on my smaller workstreams.