Repository navigation
docs: bring guides, rules and examples in step with commit-check 2.19.2 - #57
Merged
Merged
Conversation
✅ Deploy Preview for commit-check ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing: 14
✨ Finishing Touches
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. Comment |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 docs-sync test was red on main (
rev: v2.19.1in five places, but 2.19.2 is on PyPI). Pasted outputs and examples had drifted from what the tool prints, and some guide pages described older Action and App behaviour.After: the pins read
v2.19.2, the test passes, and every change below was checked against commit-check 2.19.2, Action v2.18.0 or the App's main branch.rev: v2.19.1rev: v2.19.2[FAIL] CC003 subject_imperative: …[FAIL] CC003 subject-imperative: …(what--compactprints)ec2-useras the failing example; "digits are rejected"12(it fails;ec2-userpasses); a correct description of the patternfix: bugas the failing example (it passes at 5)fixgit commit --amend -m …(git refuses on the empty commit from step 2)git commit --amend --allow-empty -m …allow_branch_namesdevelopmissing from always-allowed names; bare-mcalled the commit-msg hook's formdeveloplisted; the hook note moved to "From a file"12called a "one-character name" and the recorded author; hook list withoutcheck-tag/check-files;--tagdefaults missinguser.name; all seven hooks; SemVer default named--tagmissing from the defaults table--tagrow addedfetch-depth: 0"or it only sees the most recent one"; forks "fail to post";GITHUB_TOKENpassed by hand; no inputs listpr-titletip andresultoutput2 of 4 checks failedtitles; "every commit"; "fetches nothing else"Commit message and branch failed (2 of 4 checks); newest 50 per push; the metadata it readspr-titletests/docs_sync_test.py: the--compactguard compared samples with the config key, which--compactstopped printing. It now compares them with the kebab-case name.How:
pytest testspasses (10/10). The v2.19.2 items that another change covers are left out here: CC013 and the Copilot coding agent, the wrong-type config errors, the changelog, and the kernel cell in the AI-attribution article.Summary by CodeRabbit