docs: document --rev and the skip notice, and date v2.14.0 - #15
Conversation
The recipes page gains a revision tab for message checks, the author-check section explains what --rev changes about whose identity is judged, the range recipe drops the stdin pipe for --rev, and a new section documents the skip status: which rules decline merge subjects, the stderr notice, and the JSON status. Both examples are pasted from real runs. The changelog gains the v2.15.0 entry for the engine changes shipping in it and stamps v2.14.0 with its release date.
✅ Deploy Preview for commit-check ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Review limit reached
Next review available in: 57 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
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 |
The docs-sync test pins every install snippet to the released version, which became 2.14.0 today.
1 participant
Documentation for the engine changes merged in commit-check/commit-check#544, ahead of the v2.15.0 release, plus the release date for v2.14.0.
Command-line recipes (example.md)
--revtakes anythinggit rev-parseunderstands, errors up front on a revision that does not resolve, and refuses to be combined with a message file or stdin.--revit is the local git config (right for a hook, wrong for CI); with--revit is that commit's recorded author, and the config is never consulted.--rev, which also lets it include the author checks meaningfully, and showsgit rev-list HEAD^1..HEAD^2for covering exactly a PR's commits.Merge/fixup!prefixes qualify, the one-line stderr notice, the JSON"status": "skip", and a warning box about the synthetic-merge-commit trap onpull_requestcheckouts.Both console examples are pasted from real runs of the current engine, not written by hand.
Changelog
--rev, the stdin-hang fix, skip visibility, and the tightened merge/fixup bypass.mkdocs build -spasses (social cards disabled locally — the build environment cannot reach fonts.google.com; nothing in this diff touches that path).