Bugfix Branch Naming Convention
Create clear bugfix branch names that reference the bug ticket and describe the fix, helping teams track bug resolution through the development pipeline.
Detailed Explanation
Bugfix Branch Naming
Bugfix branches address known defects discovered during development or QA testing. They differ from hotfix branches in that they are not urgent production issues — they are scheduled fixes for the next release cycle.
Standard Format
bugfix/{ticket}-{description}
Examples
| Bug Ticket | Description | Branch Name |
|---|---|---|
| BUG-456 | Fix login redirect loop | bugfix/bug-456-fix-login-redirect-loop |
| #1023 | Correct timezone offset | bugfix/1023-correct-timezone-offset |
| ISSUE-78 | Resolve memory leak in cache | bugfix/issue-78-resolve-memory-leak-in-cache |
Bugfix vs Hotfix
Understanding the distinction is important for workflow consistency:
| Aspect | Bugfix | Hotfix |
|---|---|---|
| Urgency | Scheduled, non-critical | Urgent, production-impacting |
| Branch from | develop or main |
main or production |
| Merge to | develop → main |
main directly, then back-merge |
| Review | Standard PR review | Expedited review |
Naming Best Practices for Bugfixes
Start the description with an action verb that indicates the nature of the fix: fix-, resolve-, correct-, patch-, or repair-. This makes the branch name self-documenting. For example, bugfix/BUG-456-fix-null-pointer-on-login instantly tells any team member what the branch addresses without needing to look up the ticket.
When the bug affects a specific component, include it in the name: bugfix/BUG-789-fix-sidebar-overflow-on-mobile. This helps when multiple bugs are being fixed simultaneously and reviewers need to understand the scope of each change.
Use Case
A QA engineer files a bug report for a login page that enters an infinite redirect loop when the session expires. The developer needs a branch name that clearly indicates this is a bug fix, references the ticket, and describes the issue.