You should create a guide/rule on how you want contributors to create branches: : Best Practices #18
Description
I did not see anywhere specifically mentioned how you would like the branches a contributor needs to be created, i.e:
- From what Branch
- How do you want it stated, for example "Feature/short-description", "Issue/short-description"
- What branch should the PR be merged into, the previous issue here created comes into play here by creating other branches (You should create a development branch aside for the default branch: Best Practice #14)
The naming of branches just help people understand what the PR is about more a less and with GitHub if you specify a branch with "Feature/short-description" it can create a title for you when you create a PR.