What is a good git branch naming convention?
Most teams settle on <type>/<TICKET-KEY>-<short-title>, for example feature/PROJ-142-add-feed-pagination. The type prefix groups branches in tooling, the ticket key links the branch back to the issue tracker, and the slugified title says what the branch does without anyone opening it. Keep the title lowercase, use one separator throughout, and stay somewhere around 60 characters.
How do I turn a JIRA ticket into a branch name?
Paste the whole issue link — https://your-company.atlassian.net/browse/PROJ-142 — followed by the issue summary. The key PROJ-142 is pulled out of the link, the rest becomes the slugified title, and every prefixed variant is generated at once. A key inside a URL always wins over one in the surrounding text, because that is the issue you actually linked.
Which branch prefixes should I use?
feature/ for new work, bugfix/ for a defect on the current line, hotfix/ for something going straight to production, release/ for a version being cut, chore/ for maintenance, docs/ for documentation, refactor/ for changes that keep behaviour, and test/ for test-only work. Generate them all and copy the one that fits, or untick the types your team does not use.
Should a branch name use hyphens or underscores?
Both are legal in a git ref, and hyphens are the common default — they match the ticket key and read better in a pull-request list. Underscores suit teams whose tooling already uses them. Switch with the word separator option; the ticket key keeps its own hyphen either way, so PROJ-142 stays greppable and JIRA still matches the branch to the issue.
Why is the ticket key kept uppercase?
Because it is an identifier, not a word. JIRA and most trackers match branches, commits and pull requests on the exact key, so PROJ-142 is left uppercase and keeps its own hyphen even when the title is lowercased and the separator is an underscore. Turn on "Lowercase TICKET-123" if your team prefers it lowercased anyway.
How long should a git branch name be?
Git has no practical limit, but branch names are typed, tab-completed and read in review queues, so shorter wins. The budget here is 60 characters for the whole name including the prefix, adjustable between 12 and 200. A name that does not fit is cut back at a word boundary rather than mid-word, and the row tells you it was trimmed.
Which characters are allowed in a git branch name?
Git rejects spaces, the characters ~ ^ : ? * [ and \, the sequences .. and @{, a trailing .lock, and leading or trailing dots and slashes. Rather than police that list, the generator only ever emits a–z, A–Z, 0–9, your separator and the / after the type prefix. Accents are transliterated, so "Zmień hasło" becomes zmien-haslo, and anything else collapses into a separator.
Is anything I paste sent to a server?
No. The page is static and the whole generator runs in your browser: there is no backend, no analytics and no network request at runtime. Ticket titles, internal project keys and customer names never leave the tab, which is the point — you can paste straight from a private tracker.