<author>/<type>/<ticket>/<title>
revett/feature/24101/skeleton-service-for-email-sender
GitHub username.
bug - Code changes linked to a known issue
feature - New feature
refactor - Code refactoring
spike - Experiments
Ticket/story ID.
- Use
kebab-case
- Keep it concise
I don't think it's constructive to have branch name guidelines. Branches are supposed to be transient -- as long as the branch names are unique enough that people aren't conflicting, I don't see the problem in calling your branches whatever you feel like.
That's not to say that I disagree with having meaningful branch names as a courtesy to yourself and others. The style I use is
#{JIRA-ref}-#{meaningful-description}
e.g.NEWS-1234-fix-the-thing
. Although lately I've been dropping the JIRA project ID, e.g.1234-fix-the-thing
which makes it easier to autocomplete branch names on the command line.