Git branch names and workflow
June 17, 2019
For a long time at Multiple States we would include the version number in every branch name (eg master_1.2.3_kb_issue123). This has caused some issues as regularly on larger projects priorities change and things will go in to different branches. This causes confusion on pull requests.
I am looking at this new branching naming system:
This allows for issue / fixes to merge to different branches if needed.