Branch Naming Conventions

Core guidance

Adopt predictable branch naming patterns to improve collaboration, automation, and debugging.

Why it matters

Good Git practice is less about looking clever with commands and more about keeping history readable, collaboration predictable, and recovery paths clear.

Checklist

• Make names reflect branch type and topic
• Standardize prefixes across the team
• Avoid mixing temporary and long-lived naming styles

Commands to review alongside it

It usually helps to review this topic alongside git status, git log, and git diff, then add git rebase, git merge, or force-with-lease where appropriate.