Git Branch Name Generator
Turn ticket titles into conventional git branch names (feat/, fix/, chore/) with slugify, ticket prefixes, separator options, and length limits.
Loading tool...
What is Git Branch Name Generator?
The Git Branch Name Generator converts a ticket title or feature description into a clean, conventional branch name. It slugifies your text, prefixes it with a type like feat/ or fix/, optionally adds a ticket ID, and enforces a maximum length — producing names such as fix/prod-123-login-page-crash-email-empty.
Key Benefits
- Consistent branch names across the whole team without bikeshedding
- Type prefixes make git history and PR lists scannable
- Ticket ID prefixes keep branches linked to Jira or GitHub Issues
- Length limits prevent messy truncated names in tabs and logs
- Works entirely in your browser with no account or server
Common Use Cases
- •Creating a branch from a Jira or GitHub ticket title
- •Enforcing a feat/fix/chore naming convention for new contributors
- •Generating a ready-to-run git checkout -b command quickly
- •Producing short, readable branch names for long feature requests
How to Use the Git Branch Name Generator
- Paste your ticket title: Type or paste the ticket title or feature description, for example "Fix login page crash when email is empty".
- Add a ticket ID (optional): Enter an issue key like PROD-123 to prefix the branch so it links back to your tracker.
- Pick type and options: Choose the branch type (feat, fix, chore...), a hyphen or underscore separator, and a maximum length.
- Copy and create: Copy the generated branch name or the ready-to-run git checkout -b command and paste it into your terminal.
Key Features
- Generates conventional branch names from any ticket title or feature description
- All 11 common branch types: feat, fix, chore, docs, refactor, test, style, perf, ci, build, revert
- Optional ticket or issue ID prefix (e.g. PROD-123) for traceability
- Hyphen or underscore word separators with stopword removal for concise names
- Configurable maximum length that truncates cleanly on word boundaries
- One-click copy for the branch name and a ready-to-run git checkout -b command
Frequently Asked Questions
What is a conventional branch name?
A conventional branch name starts with a type prefix such as feat/, fix/, or chore/ followed by a short slug describing the change, for example feat/user-profile-page. The convention mirrors Conventional Commits and makes history readable at a glance.
Why is there a maximum branch length?
Long branch names clutter tab bars, logs, and pull request titles. Most teams cap branch names around 50-70 characters; the generator truncates cleanly on a word boundary so the name never ends in a half-word.
Should I include the ticket ID in the branch name?
It is optional but recommended. A prefix like PROD-123/ lets trackers such as Jira or GitHub Issues automatically link branches and pull requests back to the ticket.
Hyphen or underscore in branch names?
Both are valid in git. Hyphens (kebab-case) are the most common choice and read well in URLs and PR titles, while some teams prefer underscores. The generator supports both and applies your choice consistently.