<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
If this code should be deployed right after it was completed, it goes to hotfix. I think it doesn't matter what inside, bug or feature.
If this code is in plan, it should be named depending on it's purpose (bug/feature/etc).