What branch naming conventions are supported?

The tool supports the most common Git workflow prefixes: feature/, bugfix/, hotfix/, release/, chore/, fix/, docs/, and test/. You can toggle each one on or off to match your team's specific rules.

Does this tool enforce lowercase-only names?

The lowercase rule is optional. Toggle "Lowercase only" in the advanced rules panel to enable it. Many teams allow mixed case, so it is off by default.

What counts as an invalid character?

Git itself forbids spaces, double dots (..), tildes (~), carets (^), colons (:), backslashes (\), and certain other ASCII control characters in branch names. This tool flags all of them.

Can I check a JIRA-style ticket ID requirement?

Yes. Enable "Require ticket ID" in the advanced rules panel and the tool checks that your branch name contains a pattern like ABC-1234 after the prefix.

Is my branch name sent to a server?

No. All validation runs entirely in your browser. Nothing is ever transmitted to any server.

What is the recommended maximum branch name length?

Most teams and hosting providers work well with names under 100 characters. The default max length in this tool is 100, but you can adjust it.

Branch Naming Convention Checker

Name: Branch Naming Convention Checker
Availability: InStock
Author: Nham Vu

Paste a Git branch name and instantly see whether it passes your team's naming conventions, with clear violation details.

Branch Name

Try:

Allowed Prefixes

At least one prefix must be enabled. Toggle to match your team's workflow.

Advanced Rules

Lowercase only

No uppercase letters allowed after the prefix

Require ticket ID

Body must contain a pattern like ABC-1234

No consecutive hyphens

Disallow -- in the branch body

Max length

Maximum characters allowed

Enter a branch name

Type a branch name on the left to see validation results.

Load a Workflow Preset

Copied!

Summary

Paste a Git branch name and instantly see whether it passes your team's naming conventions, with clear violation details.

How it works

Enter or paste a Git branch name into the input field.
Toggle the allowed prefixes (feature/, bugfix/, hotfix/, etc.) to match your team's rules.
Optionally enable advanced rules such as lowercase-only, max length, or ticket ID requirements.
The checker validates your branch name in real time against all active rules.
Each failing rule is highlighted with a clear explanation so you can fix the name immediately.

Use cases

Verify a branch name before pushing to a repository with strict CI naming gates.
Onboard new developers by showing them exactly what a valid branch name looks like.
Debug why a branch was rejected by a pre-receive hook or pipeline rule.
Explore different convention presets (GitFlow, trunk-based, GitHub Flow) to pick the right one.
Quickly check ticket-ID requirements (e.g., JIRA-1234) embedded in branch names.
Test edge cases like slashes, uppercase letters, and special characters.

Frequently Asked Questions

Last updated: 2026-06-09 · Reviewed by Nham Vu