Skip to main content

Skipping commits

You can use --skip-commit argument to skip specific commits by their SHA1 value:

git cliff --skip-commit a78bc368e9ee382a3016c0c4bab41f7de4503bcd

If you have multiple commits to skip, you can either use this argument multiple times or create .cliffignore at the root of your repository.

For example:

# contents of .cliffignore

4f88dda8c746173ea59f920b7579b7f6c74bd6c8
10c3194381f2cc4f93eb97404369568882ed8677

Using .git-blame-ignore-revs file​

As an alternative, if the repository has a .git-blame-ignore-revs file, git-cliff automatically excludes:

  • commits whose hash (full or abbreviated) is listed in that file, and
  • commits that only modify that file.

For example:

# contents of .git-blame-ignore-revs

4f88dda8c746173ea59f920b7579b7f6c74bd6c8
10c3194381f2cc4f93eb97404369568882ed8677

This mirrors what git blame --ignore-revs-file already does for blame output, keeping large, non-semantic commits (e.g. mass reformatting) out of the changelog. This has no effect if the file does not exist.