Check commit subject style - #3
Conversation
|
Warning Review limit reached
Next review available in: 37 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 Plus Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe commit-message action now checks subject capitalization, trailing periods, imperative mood, and maximum length. The validator records style violations and imperative suggestions. Diagnostics and success messages include the new subject-style requirements. Tests cover rejected and accepted subject forms. Documentation and the action description reflect the updated checks. Possibly related PRs
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
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 |
cccb970 to
0f2d9b5
Compare
Table-driven cases obscure which inputs are accepted and what each failure reports. Use focused assertion helpers so the policy examples read directly.
0f2d9b5 to
e08a4dc
Compare
The shared checker accepts malformed and common past-tense subjects, so local and CI checks do not enforce common Airlift commit style. Reject those forms with specific guidance.
e08a4dc to
98d0578
Compare
2 participants
The shared checker currently accepts malformed and common past-tense
subjects, so projects cannot rely on it for consistent commit history.
Reject lowercase starts, trailing periods, and ten common past-tense starts
with actionable guidance.