<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
For the title/description dev can mention it on the pull request or the scrum master can check the details from UserStoryPBI/Bug number on DevOps.
For Example:
for PBI: PBI--DDMMYYYY(startdate)
for User Story: US--DDMMYYYY(startdate)
for Feature: Feature--DDMMYYYY(startdate)
for Bug: Bug--DDMMYYYY(startdate)
for Task: Task--DDMMYYYY(startdate)
The title is not necessary to mention in the branch name because sometimes a branch can contain multiple fixes, It's better to mention the related work on OR OR .