DEV Community

Git Branch Naming Convention

couchcamote on March 31, 2020

Working on a big company with projects that could scale from a one-man team then suddenly to a 20 developers team, having a manageable code reposit...

Read full post

Shahed • Dec 21 '20 • Edited

Very thorough summary of all usual conventions. Just want to add after the Black Lives Matter movement, git provided option to use names other than master, the option is: git init --initial-branch=stable. Hence technically speaking master is deprecated in favour of other names such as stable or main.

jstewart8053 • Jan 26 '21 • Edited

You mean after the Black Lives Matter movement. It's not a 'thing'. smh
Very helpful post though, what do you think about emojis in commits? I have seen a lot on the issue lately.

Shahed • Feb 5 '21 • Edited

Sure you are right, since English is not my native language 😅. The correct word is movement, and thanks. I edited my original reply.

jstewart8053 • Feb 9 '21

No worries :)

Ravi Ponamgi • May 6 '21

Liked "No worries", considering the OP was made with the best of intentions.

EvilKittenLord • Oct 2 '23

Everything needs a naming scheme. :)
Folks might be interested in the naming scheme I've been using that enables automatic semver detection.
github.com/marketplace/actions/git...

federico • Sep 20

2024 and this post is still awesome.

For those who are interested in naming conventions for commits, I found this post that builds on this one.

Clifton Long Jr. • Aug 30 '20

Great post, and very helpful! 😄

Eduardo Zepeda • Nov 10 '20

This is so useful, most people should read this post.

slidenerd • Jul 15 '22 • Edited

What do you call a branch where you start a python project empty, add a gitignore, readme, poetry, tox, pre-commit, add a main.py setup pyproject.toml install pytest and run some tests inside the tests directory which you also create

Roberto Tonino • Aug 19 '20

Great post, thanks! Definitely gonna use this convention :)

I would suggest a branch for dependencies upgrading too (expecially ones with breaking changes), what do you think?

couchcamote • Oct 15 '20 • Edited

Glad to have helped.
For new dependencies upgrading we can consider that as a new feature. Basically, it is like new code changes with new libraries and code updated to use them. It should also follow the dev-test-stage-prod flow and it usually has planned schedule for release.