More Flexible branch naming rules for related branch detection
Problem to solve
If you want to automatically link an issue to a branch you have to start the branch name with the issue number followed by a dash like this example: "102-GreatFeature".
Further details
This is very little flexible. You can't place the number at the end (like "GreatFeature-102" and grouping/folders are not supported (like: "feature/102-GreatFeature".
Grouping into folders with the "/" are sometimes useful as most editors (e.g. SourceTree) groups them together in folders. This is broken when adding the issue number first.
Proposal
One solution is to search for a tag, e.g. # followed by a number. This is rarely used in branch names and could be placed every where in the branch name and there are no need for the dash as long as only numbers are recognised.
Example of supported names: #102 (closed)-GreatFeature GreatFeature#102 GreatFeature-#102 feature/#102 (closed)-GreatFeature
An alternative solution is to start searching for the issue number right after the last "/" in the name. This is less flexible as the first suggestion but is still an improvement.
What does success look like, and how can we measure that?
An success is if "/" are supported. A greater succes are if more flexibility is added as well.