Git Branch Name Generator

When to use?

Use it to keep consistent naming when creating a branch, to quickly turn a task title or issue into a branch name, or to match your team's branch naming convention.

How to use

• Enter the task title or description.
• Choose the branch type (feature, fix, hotfix, etc.) and issue number.
• Copy the generated branch name and git checkout command.

Input Explanation

Specify the task title, branch type, issue/ticket number (optional), and separator (/ or -). The title becomes lowercase-hyphen form.

Calculation Basis

It lowercases the title, replaces spaces/special characters with hyphens to make a slug, then combines the branch type and issue number. Length is capped at 60 characters.

Usage Examples

• Consistent branch naming - Make same-convention branch names per task to keep collaboration clean.
• Issue-linked branches - Quickly generate branch names including an issue/ticket number.
• Generate checkout command - Generate the git checkout -b command to run directly.

Examples

• "Login page dark mode support" + feature → feature/login-page-dark-mode-support
• Add issue 142 → feature/142-...

Cautions

• Generated output is for reference; test carefully before production use.
• Git supports non-Latin branch names, but English titles are recommended for collaboration.

Guides

Branch naming conventions

Branch names are usually lowercase with hyphens and a type prefix like feature/ or fix/. A consistent convention makes branch lists easy to read in collaboration.

Linking issue numbers

Including an issue/ticket number in the branch name links the work to the issue easily. Non-Latin branch names work, but English is recommended.

FAQ

Can I use a non-Latin title?

Git supports non-Latin branch names, but English is recommended for collaboration; a notice appears when non-Latin is included.

Which branch types are available?

feature, fix, hotfix, refactor, chore, docs, test, release, and you can also make one without a prefix.

Which separator do I choose?

Choose between the slash (feature/name) and hyphen (feature-name) per your team rule.

Is there a length limit?

The title slug is capped at 60 characters to avoid overly long branch names.

Related Tools

• Gitignore Generator - Generate gitignore templates by language/framework.
• Slug Generator - Convert a title or sentence into a URL-friendly slug string.
• UUID Generator - Generate up to 20 cryptographically secure UUID v4 values at once.
• semver Comparator - Compare two semantic versions and interpret version range notation.
• Case Converter - Convert text, variable names, and filenames to UPPER, camelCase, snake_case, kebab-case, and more.
• JSON Formatter - Beautify or minify JSON strings instantly and check for validity errors.