docs(rules): configure the rules audit per repo for org-wide reuse#131
Conversation
Time Submission Status
Submit or update total time with: Add time on top of previous submission with: See available commands to help comply with our Guidelines. |
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughThe rules audit now reads a repository-specific ChangesRules audit configuration and validation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
✨ Finishing Touches🧪 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 |
zolotokrylin
left a comment
There was a problem hiding this comment.
@holdex pr submit-time 11m
zolotokrylin
left a comment
There was a problem hiding this comment.
@holdex pr submit-time 7m
Problem
The rules audit hardcoded this repo's layout (id prefix, index path, heading levels, link style, web-app root-README checks), so no other repo could run the same script without forking it.
Solution
Moves every repo-specific setting into
rules.config.yml, soscripts/check-rules.mjsis identical in every repo that adopts the standard and only the config differs. Behavior here is unchanged: the audit still passes on 34 rules, and a negative test confirms it still catches missing headings and dashes.Configurable settings: id prefix, rules dir, index file, filename style (id vs id-slug), title-as-H2, Problem/Solution/Acceptance heading levels, link style (inline vs reference), required frontmatter fields, Problem length cap, and toggles for Acceptance Criteria, no-dashes, lower-id dependencies, docs-spine reachability, and the root-README checks.
Related
Summary by CodeRabbit
New Features
Documentation