Branch Name Convention Validator
Check Git Flow, prefix and kebab-case, ticket-based or custom regular-expression policies. Compare Git syntax issues with policy findings and export a batch report.
Distinguish Git Errors From Branch Policy
Find & replace in input
Undo: Ctrl/Cmd+Z · Redo: Ctrl/Cmd+Shift+Z or Ctrl+Y. Up to 20 steps and 4 million retained characters in this tab. Clear discards history.
Branch Name Convention Validator: how to use it
- Paste literal branch names, one per line. Choose Git Flow, a prefix policy or a custom regular expression.
- Set the length and lowercase rules. When using a prefix or ticket policy, configure the prefixes and ticket syntax to match your team's convention.
- Check branch names. Read the Git and policy findings under each source line, then copy or download the JSON report.
Limits and notes
Up to 500 nonblank lines and 256,000 UTF-8 bytes. Length limits range from 1 to 512 Unicode code points. Each pattern supports 512 characters and a three-second check. Verify existing branch names and remote restrictions in the relevant repository.
How your privacy works →Branch Name Convention Validator: common questions
Can my branch contain an uppercase ticket like OPS-42?
Choose the ticket profile and match the ticket with its regular expression. The lowercase toggle requires lowercase in the prefix and description while allowing the matched ticket token to keep its case.
Which protected names can pass without a prefix?
The option allows main, master, develop, staging and production through the naming profile while retaining Git's syntax and the length limit.
Can I check if the branch already exists or is protected remotely?
This report checks literal strings and the rules you selected. Check your repository and hosting provider for branch existence, worktree state and enforced restrictions.