This blog post kicks off a series related to Git, what I consider to be some of the best practices when using git on the daily basis, the tips and tricks I know for sure have impacted my team and our daily workflows when working on new features, fixing bugs and reviewing code.
Some of the tips and tricks are really simple and nothing more than common sense, some others require a little bit of Git knowledge, in all cases I will be providing examples for a better understanding and the rationale behind the tip or trick.
Please be aware, we follow the feature branch workflow, so all the tips are based on that workflow.
Let’s get this thing started.
Branch naming conventions
Naming the branch is the first thing to do when working on any new change. The new branch will follow this pattern:
Naming the branches this way give us the following three benefits:
Humanized names are simpler to understand
Having the ticket type in the branch name itself is always useful, because obviously you can tell from a chore and a fix, specially useful when managers or team leads want to see what new fixes are being implemented, doing a simple as:
git branch -r | grep "fix/" | wc -l
If for whatever reason a ticket in particular has to be divided and there’s no way to create multiple subtickets for each specific change, then multiple developers can work on their own personal feature branches and still reference the same ticket number.
Ideally, in the perfect world, no developer should be using the same ticket number, so for example branches like these should never be happening:
When using a CI, like Gitlab-CI, Jenkins or Travis. You can selectively build the branches that match certain patterns, let’s say only those beginning with fix or feature. The idea is to save some precious computing time for all other branches that really require CI.