Fill in a description above…
Clean branch names following team conventions
← devnestioGit Branch Name Generator creates properly formatted branch names from task descriptions or ticket numbers. Enter a description (e.g., 'fix login button on mobile') or ticket ID (e.g., 'JIRA-1234') and get a clean, convention-compliant branch name: feature/fix-login-button-mobile, fix/jira-1234-login-button, or hotfix/login-button-mobile — matching common team naming conventions.
Well-formatted branch names improve developer experience and repository hygiene. Conventions: use hyphens (not underscores or spaces), lowercase only, prefix with type (feature/, fix/, hotfix/, chore/, refactor/, docs/), include ticket number when applicable, keep under 50-60 characters, avoid special characters except hyphens and forward slashes. Teams using Jira, Linear, or GitHub Issues often auto-generate branch names from these systems.
Branch naming conventions affect: pull request titles (many tools auto-populate from branch name), branch list readability, automated deployment rules (only deploy feature/* branches, not main), merge queue ordering, and the ability to auto-link branches to tickets. Consistent naming reduces cognitive overhead for the entire team.
Task: 'Add user profile picture upload'
Result: feature/add-user-profile-picture-upload → git checkout -b feature/add-user-profile-picture-upload
Bug ticket: JIRA-2341 'Login timeout'
Result: fix/jira-2341-login-timeout → git checkout -b fix/jira-2341-login-timeout
Hotfix: 'Payment processing fails'
Result: hotfix/payment-processing-fails → git checkout -b hotfix/payment-processing-fails
What are the most common git branch naming conventions?
Common patterns: (1) Prefix by type: feature/name, fix/name, hotfix/name, chore/name. (2) Ticket-first: JIRA-1234-description or 1234-fix-login. (3) User-prefixed: username/feature-name (common in large open source projects). (4) Date-based: 2026-07-release (for release branches). Most teams standardize through .git/hooks, branch protection rules, or GitHub Actions workflows that reject non-compliant branch names.
What is the difference between feature, fix, and hotfix branches?
feature branches: new functionality added to the codebase. fix branches (also called bugfix): bug corrections that go through normal development and review cycle. hotfix branches: urgent fixes that bypass normal review and are merged directly to main/master with expedited review — typically for production-critical bugs. chore branches: maintenance work (dependency updates, build configuration) with no user-facing changes. This semantic naming communicates urgency and type to the whole team.
Why should branch names use hyphens instead of underscores?
Hyphens are URL-safe (no encoding needed), work in most shell contexts without quoting, are readable in terminal output, and are conventional in git workflows. Underscores work but are visually harder to distinguish in some fonts and terminal color themes. Spaces are prohibited in git branch names (they break git commands). Some teams use forward slashes for type prefixes (feature/) which git treats as path separators, creating a visual hierarchy in git clients.
How do I enforce branch naming in CI/CD?
Several approaches: (1) Git hooks (pre-push): reject pushes if branch name doesn't match a regex. Add to .git/hooks/pre-push: branch=$(git symbolic-ref HEAD); if ! [[ $branch =~ ^refs/heads/(feature|fix|hotfix)/ ]]; then exit 1; fi. (2) GitHub Actions: add a workflow that checks the branch name on push and fails if it doesn't match. (3) Branch protection rules (GitHub, GitLab): use patterns to control which names can be merged. (4) Danger JS/Ruby in PR checks.
How long should a git branch name be?
Under 50-60 characters is a practical limit. Very long names are cumbersome to type, truncate in git GUIs and terminal output, and make git log --oneline hard to read. Very short names (fix/bug) lack enough context. Sweet spot: 15-40 characters after the prefix, specific enough to identify the work without the full ticket title. If a ticket title is too long: use the ticket number instead of trying to fit the whole title.