Cargo Cult and Branch Names

Leo Soto
Leo Soto
Jan 11, 2019 · 1 min read

I’ve seen (and worked on) projects which tell you to name branches with a chore or fix or feat prefix. Why is that?

If branches are short lived, I don’t get the point. Whatever goes after the prefix is the key part, which describes the branch. I don’t see whatfeat/login-with-fingerprint buys me vs login-with-fingerprint. In both cases I expect the commits (and pull requests, if used) to go deeper on the what and why.

Is it supposed to help you when you have long lived branches? It’s hard to understand that point. Again whatever describes the branch (login-with-fingerprintin previous my example) will end up being more useful when navigating the branches than the “category” . If you have few long lived branches, the category won’t really help. If you have tons of long lived branches, same thing!

Maybe some teams have just the right amount of active branches (not few but not a lot) that the “category” prefix help them navigate the current state of the repo? That’s fine.

Maybe then other teams/individuals just mindlessly copied the practice to other projects where it doesn’t help at all? That’s sad.

Or am I missing something? What’s the point of branch prefixes?

Leo’s Tech Blog

A personal blog on tech stuff.

Medium is an open platform where 170 million readers come to find insightful and dynamic thinking. Here, expert and undiscovered voices alike dive into the heart of any topic and bring new ideas to the surface. Learn more

Follow the writers, publications, and topics that matter to you, and you’ll see them on your homepage and in your inbox. Explore

If you have a story to tell, knowledge to share, or a perspective to offer — welcome home. It’s easy and free to post your thinking on any topic. Write on Medium

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store