fix(scheduler): run bounded review repairs every hour - #1006
Conversation
|
Warning Review limit reached
Next review available in: 3 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
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 |
|
@opencode-agent @cwl-noema-review Please independently review exact head |
Pull request was converted to draft
|
@coderabbitai review Please review the unchanged exact head |
|
I will verify the hourly cron, one-hour same-head retry,
|
|
Closing this narrower cadence-only PR as superseded by #782. PR #782 already carries the hourly review-repair cadence together with the required NVIDIA NIM credential separation, exact-head RCA/repair contract, bounded writer scope, fail-closed behavior, and repository-specific callers. Keeping both open would race on |
Pull request was closed
Outcome
Run the central review-feedback repair scheduler once per hour instead of once every two hours, while preserving its bounded and fail-closed operating contract.
23 */2 * * *to23 * * * *;max_dispatches = 1, head-scoped repair markers, target-repository concurrency, and canonical central workflow ownership;CHANGELOG.md.The merge scheduler already performs organization sweeps every 15 minutes; this PR only raises the slower code-repair loop to the requested hourly cadence. It does not duplicate scheduler logic into application repositories or alter review-agent credentials.
Merge only after exact-head quality/security checks and an independent review. Auto-merge may be enabled after the repository validates this head.