docs(claude): apply review fixes to the canonical-resource-model rule - #754
Conversation
Follow-up to #753, which merged before the independent review's fixes landed: correct the stale control-plane/ path in the pre-existing config-knob rule (the file lives at the repo root of AISIX-Cloud), mark the cross-plane contract check as planned, state the #644/#657 cost precisely (churn, not incidents), and carve out unreleased fields from the no-hard-rename rule.
|
Warning Review limit reached
Next review available in: 48 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. ✨ 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 |
1 participant
Follow-up to #753 (merged before the review fixes landed). Applies the independent review's findings: 1 MEDIUM — the pre-existing config-knob rule cited
control-plane/openapi/cp-admin.yaml, a path that does not exist (the spec lives at the AISIX-Cloud repo root); plus three wording precision fixes (contract check marked as planned; #644/#657 described precisely; unreleased-field carve-out on the no-hard-rename rule).