About git branch name generator
A consistent branch name helps teams see what a branch is for. The tool turns a ticket ID and description into a clean name.
Good conventions
- Use a prefix such as feature/, fix/ or chore/.
- Include the ticket ID if you use a tracker.
- Use lowercase and hyphens, and keep it short.
A worked example
For ticket PAY-142 with the description 'Fix rounding error in invoice total', the tool gives fix/PAY-142-fix-rounding-error-in-invoice-total, with lowercase words and hyphens. Long names are shortened sensibly, so they stay readable in the terminal.
Why naming helps
- Team members can tell the purpose of a branch at a glance.
- Issue trackers can link branches to tickets automatically.
- Prefixes allow filters such as listing every fix/ branch.
Branch hygiene
Delete merged branches, both locally and on the remote, so the list stays short. Use git branch --merged to see which ones are safe to remove.
