You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: pin v2.21.1 and document the CC004 squash suffix and bot skip - #87
Before: the site describes 2.21.0. The six pre-commit snippets pin rev: v2.21.0, the changelog stops at v2.21.0, and CC004 / CC005 count every character of the subject, for every author.
After: the site describes 2.21.1, published 2026-11-18.
All six snippets pin rev: v2.21.1.
The changelog has a v2.21.1 entry (three fixes) and a Highlights row, since the length rules now judge subjects differently.
CC004 gets a "Not counted" part: the (#123) a squash merge adds, and commits by dependabot[bot] and renovate[bot]. CC005 points to it.
The subject_max_length and subject_min_length rows in "Every option" say the same.
What the released 2.21.1 prints:
$ echo"fix: return 404 if no member left after pick and omit when retrieving an entity (#1698)"| commit-check -m
$ echo$?0
$ echo"feat: <80 characters> (#1698)"| commit-check -m✖ CC004 subject-max-length failed: feat: aaaa…aaaa (#1698) Subject is 86 characters, not counting "(#1698)"; it must be at most 80 characters Suggest: Shorten the subject by 6 characters, to 80 or fewer
$ echo"chore(deps): Bump org.zalando:logbook-spring-boot-webflux-autoconfigure from 4.0.3 to 4.0.4"| GIT_AUTHOR_NAME='dependabot[bot]' commit-check -m⊘ skipped (not validated): subject-max-length
2.21.0 failed the first and third.
How
tests/docs_sync_test.py passes against the installed 2.21.1 (18 tests) and mkdocs build --strict is clean.
Blog posts keep their pins, as AGENTS.md asks.
Summary by CodeRabbit
Bug Fixes
Subject-length checks now exclude GitHub squash-merge suffixes and are skipped for Dependabot and Renovate commits.
Force-pushed commits not present in the local clone are checked against push and file rules.
Documentation
Updated configuration examples to use version 2.21.1 and clarified the subject-length exceptions.
The documentation adds v2.21.1 release notes, describes subject-length exclusions for squash-merge suffixes and dependency-bot commits, and updates pre-commit examples to use v2.21.1.
The changelog, configuration reference, and rule descriptions document the squash-merge suffix and dependency-bot exclusions. The changelog also describes checks for pushed commits that are absent from the clone.
Update pre-commit example revisions docs/compare/tools.md, docs/configuration.md, docs/example.md, docs/guides/pre-commit.md
The docs change describes v2.21.1 behavior slightly more broadly than the tool implements it. The suffix wording, bot identification for supplied messages, and forced-push coverage should be tightened before merge, but nothing here affects runtime behavior.
Pre-merge checks: 2
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title names two changes that appear in the changeset: the pin to v2.21.1 across documentation examples (docs/configuration.md, docs/example.md, docs/guides/pre-commit.md, docs/compare/tools.md) an…
Full details: Title check
Explanation
The title names two changes that appear in the changeset: the pin to v2.21.1 across documentation examples (docs/configuration.md, docs/example.md, docs/guides/pre-commit.md, docs/compare/tools.md) and the CC004 documentation of the squash-merge suffix and bot skip (docs/rules.md). The changelog entry for v2.21.1 is also consistent with the title. The title is specific and accurate, though it omits the changelog and CC005 documentation updates, which is acceptable.
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
documentationImprovements or additions to documentation
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before: the site describes 2.21.0. The six pre-commit snippets pin
rev: v2.21.0, the changelog stops at v2.21.0, and CC004 / CC005 count every character of the subject, for every author.After: the site describes 2.21.1, published 2026-11-18.
rev: v2.21.1.(#123)a squash merge adds, and commits bydependabot[bot]andrenovate[bot]. CC005 points to it.subject_max_lengthandsubject_min_lengthrows in "Every option" say the same.What the released 2.21.1 prints:
2.21.0 failed the first and third.
How
tests/docs_sync_test.pypasses against the installed 2.21.1 (18 tests) andmkdocs build --strictis clean.Summary by CodeRabbit
Bug Fixes
Documentation