What branch name conventions do you use?

David Pinn

What, if any, conventions do you apply to the naming of branches in order to create notional groups of branches? I'm trying to validate a hypothesis to help shape a plugin idea.

This is a question for users of Stash; but StashDev might as well chip in, although I already have some idea of how you work. :-)

Do you, for example, name branches to reflect the release you intend them to be part of? Do you name them according to the software component or feature they apply to? Something else?

jhinch (Atlassian)

Hi David,

I find that there are 2 main naming convention styles within git. Hyphen separated or slash separated. GitFlow uses the latter to separate groups of branches:

e.g.

hotfixes/ANERD-9999
releases/2.1
features/totality-search

Many of the cross product teams within Atlassian use this convention. Product teams within Atlassian seem to use the hyphen approach:

e.g.

release-4.5.x
ANERD-3333-project-visualisation
1.3-ANERD-2020-ie8-fixes

I find a lot of Git experts like to use the slashes approach as it equates to directories organising branches on the filesystem