Git Branch Naming Conventions: Best Practices for Teams
4 min read
A consistent branch naming convention helps teams understand what each branch does at a glance.
Common Prefixes
| Prefix | Purpose | Example |
|---|---|---|
feature/ | New feature | feature/user-authentication |
fix/ or bugfix/ | Bug fix | fix/login-redirect-loop |
hotfix/ | Urgent production fix | hotfix/payment-crash |
release/ | Release preparation | release/2.1.0 |
chore/ | Maintenance tasks | chore/update-dependencies |
docs/ | Documentation | docs/api-reference |
refactor/ | Code refactoring | refactor/auth-module |
Format: kebab-case
Always use lowercase and hyphens. Git branches are case-sensitive, and Feature/Login vs feature/login causes confusion.
Including Ticket Numbers
feature/PROJ-123-user-auth or fix/PROJ-456-cart-total