Name a Git branch from a task

Turn a ticket or description into a valid, consistent Git branch name.

freeworks offlinenothing uploaded
ToolGit Branch Namer
Input
Output
—
Put this on your own site

The frame below runs the same code as this page, in the reader's own browser. Nothing is sent to us, and nothing is sent to you.

Pick a dark background and the text and panels follow it, so the frame stays readable on a dark page.

Preview

How it works

Words are normalized into a slash-separated ref, invalid characters and reserved sequences are removed, and an optional prefix is prepended. The result is checked against Git ref-name restrictions.

  • Slash prefixes group branches in hosting UIs.
  • Lowercase kebab words avoid shell and ref ambiguities.

Worked example

Gitflow feature with Jira ticket
Generate Gitflow-style branch names for a feature with a Jira ticket number
Input
											Type: feature
Description: add user authentication
Issue number: PROJ-123
Convention: gitflow
Output
												# Branch Name Suggestions

1. feature/PROJ-123-add-user-authentication
2. feature/PROJ-123

When to use this

Feature tickets, hotfix workflows, and pull-request templates name branches.

Edge cases

  • Different inputs can normalize to the same branch.
  • Trailing dots and double dots are invalid refs.
  • Names beginning with a dash can be confused with options.

References