Feature + config branch name practices #33
Description
Lots of our configuration repositories, use multiple branches as a way of tracking multiple related branches of configurations.
e.g.
https://github.com/ACCESS-NRI/access-esm1.5-configs/
has main, dev-preindustrial+concentrations, dev-historical+concentrations etc
and often issues can impact multiple repositories.
However the branch name procedure doesn't cover this. It looks like often we use:
{issue number}-{branch (short)name}-{issue name}
Is that the best order - should we add this to dev docs ?