Repository navigation
docs: AI-only and real-project recipes, CC017, v2.20.0 - #76
Conversation
- Policies guide: a section on running the AI check alone, with conventional_commits = false and subject length 0, as cchk.toml and as Action env vars. - CC004 / CC005 and the configuration reference: 0 turns the length rule off. - CC013 and the policies guide list Continue, Mistral Vibe and Qwen Code. Describes behaviour in the next commit-check release; merge after it ships.
✅ Deploy Preview for commit-check ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Caution Review failedThe pull request is closed. Walkthrough
Merge Risk:
|
Kubernetes, the Linux kernel, Nextcloud, pip/attrs and Fedora/FluxCD each map to a few lines of cchk.toml, plus a recipe for projects that want every commit to declare AI use (Assisted-by: none when there was none).
Adds the ai-author (CC017) rule section, the v2.20.0 changelog entry, the Python 3.11 note for the Action (ubuntu-22.04 needs setup-python), and bumps the install pins to v2.20.0.
What
Site docs for commit-check v2.20.0 and Action v2.19.0, plus AI policy recipes.
ai_attribution, with the setup ascchk.tomland as Action env vars (subject_max_length = 0turns the length rule off since 2.20.0).cchk.toml, plus a recipe for projects that want every commit to declare AI use (Assisted-by: nonewhen there was none). Each recipe was run against sample commits on 2.20.0.ai-author (CC017)section; CC004/CC005 say0turns the rule off; CC013 names Continue, Mistral Vibe and Qwen Code.ubuntu-22.04needsactions/setup-python.Before / after
conventional_commits = falseand both lengths0revNew "Recipes from real projects" section:
Not in this PR
Warp, Crush and the credit trailers go in the tool list after commit-check#672 ships.
Checks
python -m pytest tests/ -qwith commit-check 2.20.0: 18 passed.mkdocs build --strict: clean.Summary by CodeRabbit
0disables that check.