feat: sync message_pattern support from commit-check to MCP server#17
Conversation
|
Warning Review limit reached
Next review available in: 35 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #17 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 2 2
Lines 209 209
=========================================
Hits 209 209 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
message_pattern is a [commit] config option that lets users specify a custom regex for commit message validation, overriding the Conventional Commits rule. It already works through the existing config pipeline (get_default_config -> load_toml_config -> deep_merge -> RuleBuilder), but was missing test coverage. Changes: - Add tests: message_pattern overrides conventional commits, and fails on pattern mismatch
e7d9dc0 to
2c0f8f5
Compare
Updated link for the Official MCP Registry and removed outdated information.
Summary
message_patternis a[commit]config option incommit-checkthat allows users to specify a custom regex pattern for commit message validation. When set, it takes precedence over the auto-generated Conventional Commits regex — useful for JIRA-style tickets likePROJ-123: description.Since the MCP server delegates to
commit-check's library (viaget_default_config(),load_toml_config(),deep_merge(), andRuleBuilder()),message_patternalready works through the existing config pipeline. No code changes to the server logic are needed.This PR adds:
message_patternworks via the inlineconfigparameter (pass on match, fail on mismatch)message_pattern(v2.8.0+) andai_attribution(v2.11.0+) as supported config featuresVerification
All 67 tests pass:
Related
See commit-check PR #427 for the original
message_patternimplementation.