commit-format 0.2.0

A tool to check git commit messages format

commit-format

A tool to check your commit messages format.

Supported checkers

Primarly disigned for to check for spelling mistakes in commit messages, commit-format now comes with various checker allowing to:

• Check that each message lines does not exceed a length limit.
• Check for spelling mistake on commit messages.
• NEW Check commit header/body/footer against a defined template.

Installation

$ pip install commit-format

Help command will show you all availables options:

$ commit-format --help

Format options

-l (--limit INT) Line limit check

You can check that every line in the commit message (including the title/header) does not exceed a length limit. By default the value is set to 72.

A limit of '0' --limit 0 will disable the line limit checker.

Usage:

$ commit-format -l 80

-ns (--no-spelling) Disable spelling mistake

By default, commit-format checks for common spelling mistakes in the commit messages.
This option rely on codespell and may produce some false-positive results.
This new option -ns --no-spelling let the user disable the spelling checker.

$ commit-format -ns

-t (--template FILE) Template compliance

You can provide a simple INI template to validate the commit header/footer format and required symbols.

Usage:

$ commit-format -t /path/to/template.ini

Template schema (INI):

• [header]
  • pattern: Regex that the first line (header) must match.
• [body]
  • allow_empty: true/false to allow a commit with only a header (no body).
  • blank_line_after_header: true/false to enforce a blank line between header and body.
• [footer]
  • required: true/false to require a footer section.
  • pattern: Regex that each footer line must match.

Example template.ini:

[header]
pattern = ^(feat: |fix: |doc: |ci: ).+$

[structure]
allow_empty = false
blank_line_after_header = true

[footer]
required = true
pattern = ^(Signed-off-by: ).+$

Behavior option

-a (--all) Force checking all commits

By default the script will only run on a branch and stop when reaching the base branch.
If run on a base branch direclty, the script will throw an error:

$ commit-format
Running on branch main. Abort checking commits.

This measure is there to prevent running the script over past commits.

If running on 'main'/'master' is required, option -a will force the script to run regadless the branch name.

Usage:

$ commit-format -a

-b (--base) Base branch name

You can set the base branch name according to your project.
As described in option -a section the base branch name is required to let the script restrict it's analysis on the commits of a branch.
Default value for the base branch name is main.

Usage:

$ commit-format -b master

-v (--verbosity)

Diplay debug messages from the script.