ci: schedule hourly commercial readiness loop - #722
Conversation
|
Warning Review limit reached
Next review available in: 29 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 (3)
Comment |
|
Closing as redundant with the organization-governed scheduler. The active central required workflow already runs an organization-wide queue sweep every 15 minutes and handles current-head review dispatch, branch refresh, guarded auto-merge/direct merge, stale queued-run cleanup, and fail-closed policy checks. Keeping a second repository-local hourly caller would duplicate mutations, consume runner capacity, and broaden workflow-token permissions without adding a distinct reliability guarantee. The external hourly commercial-readiness task remains separate from this repository workflow. |
Pull request was closed
What
Adds an hourly repository workflow that invokes the centrally governed PR review and merge scheduler.
Each run:
mainwhen safe;The reusable workflow is pinned to immutable central commit
5983b41ace75040c1d81818171ca7d0f3653254e. The cron runs at minute 17 of every UTC hour to avoid top-of-hour runner contention. A manual dispatch entry point is retained for incident recovery and immediate queue sweeps.Security and operations
CHANGELOG.mdrecords the operational capability.