111 | | * bugfix branches, in which we have a branch for each bugfix to patch, branched from a stable branch. These branches can be locally. The branches are called `bugfix/#>` where the hash-symbol is a number referring to the ticket of the bug-report. |
112 | | * feature branches, in which we have a branch for each new feature, branched from master. These branches can be locally, however can be public for collaboration-purposes as well. As a naming-convention we'll call these branches `feature/#`, where the hash-symbol is a number referring to the ticket for the feature. |
| 111 | * bugfix branches, in which we have a branch for each bugfix to patch, branched from a stable branch. These branches can be locally. The branches are called `bugfix/#]/human_readable_label]` where the hash-symbol is a number referring to the ticket of the bug-report, and the `human_readable_label` an optional label to know what it's about (without knowledge of the tickets). |
| 112 | * feature branches, in which we have a branch for each new feature, branched from master. These branches can be locally, however can be public for collaboration-purposes as well. As a naming-convention we'll call these branches `feature/#[/human_readable_label]`, where the hash-symbol is a number referring to the ticket for the feature, and the `human_readable_label` an optional label to know what it's about (without knowledge of the tickets). |