Why Define Git Commit and Branch Naming Conventions and How to Enforce Them

In team development, inconsistent commit messages and branch names make reading logs difficult, so establishing clear conventions improves readability, maintenance, and automation.

Benefits of a commit message standard include better understanding of change intent, easier contribution, support for automated scripts and CI/CD, automatic changelog generation, and demonstrating professional discipline.

Branch naming without rules leads to chaotic, hard‑to‑search names like ABC-1234-Test , Hotfix-ABC-3456 , or Release-1.0 . Enforcing a pattern such as bugfix/ABC-1234 , feature/ABC-2345 , hotfix/ABC-3456 , release/1.0 makes branches searchable and clarifies their purpose for CI/CD pipelines.

How to create the conventions

Adopt the widely used Conventional Commits specification, which defines a format like JIRA-1234 feat: support async execution . The type must be one of feat , fix , docs , style , refactor , perf , test , or chore , all in lower case.

JIRA-1234 feat: support async execution
^-------^ ^--^: ^-------------------------^
|          |
|          +--> Summary in present tense.
|          
+--> Jira ticket number

Type must be one of:
    feat: new feature
    fix: bug fix
    docs: documentation change
    style: formatting change
    refactor: code refactor
    perf: performance improvement
    test: add/modify tests
    chore: build, .gitignore, tooling, etc.

Setting Git Hooks

Using Bitbucket as an example, enable the free plugin Yet Another Commit Checker (YACC) and configure it to require a valid JIRA issue, apply commit‑message regexes, and provide helpful error messages.

Commit message regex example

[A-Z\-0-9]+ .*

This enforces a JIRA ticket like ABCD-1234 followed by a space and the rest of the description.

A more complex regex can also enforce the type, scope, breaking change indicator, and subject, while handling merge and revert messages:

^[A-Z-0-9]+ .*(?<type>chore|ci|docs|feat|fix|perf|refactor|revert|style|test|Bld)(?<scope>\(\w+\))?(?<breaking>!)?(?<subject>: .*)|^(?<merge>Merge.* \w+)|^(?<revert>Revert.* \w+)

Test cases for both passing and failing messages are provided, and the results can be verified at https://regex101.com/r/5m0SIJ/10.

Branch name regex example

^(bugfix|feature|release|hotfix).*|(master)|(.*-dev)

This requires branches to start with bugfix/ , feature/ , release/ , hotfix/ , or match patterns like v1.0-dev .

Additional hook settings can enforce matching committer email/name, require JIRA issue status checks, and provide clear error messages such as:

Branches must begin with these types: bugfix/ feature/ release/ hotfix/

References:

[1] Conventional Commits: https://www.conventionalcommits.org/en/v1.0.0/

[2] Yet Another Commit Checker: https://mohamicorp.atlassian.net/wiki/spaces/DOC/pages/1442119700/Yet+Another+Commit+Checker+YACC+for+Bitbucket