<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
On a related note, it can be really useful to apply this sort of guideline to PR names and/or commit messages. @revett's suggestion is similar to how the Angular.js team do it (they do
<type>(<component>) <description>
, and I think it works really nicely.