Repository navigation
Lift the weekly window so a bot pull request can be tested now - #60
Conversation
Temporary, and the file says so. Restore `before 7am on Monday` once the CodeRabbit question is answered. Three dependency bot pull requests went more than ten hours on 2026-08-17 without a CodeRabbit review, comment, or status, while every human pull request that day got one within minutes, and #56 answered in under three minutes when asked directly. GitHub also ran a critical incident that day, 13:40Z to 21:15Z, Webhooks included, which produces exactly that silence. The observation is therefore unusable and has to be repeated on a clean day. Repeating it needs a bot pull request to exist, and the weekly window is what prevents one: branch creation is only permitted between midnight and 7am on a Monday, and it is now Monday evening, so the next natural opportunity is a week out. checkov 3.3.11 is already waiting behind the cooling period and clears it on the 20th. Nothing else about the policy moves. minimumReleaseAge still holds every update seven days, and prConcurrentLimit and prHourlyLimit still bound the rate.
|
Warning Review limit reached
Next review available in: 20 minutes Limit details: You’ve used all 3 included reviews currently available under your plan. 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Comment |
|
/run-tests |
Temporary. Restore
schedule: ["before 7am on Monday"]once the CodeRabbit question is answered. The file carries the same note so it explains itself if we forget.Why
Three dependency bot PRs (#53, #54, #55) went more than ten hours on 2026-08-17 with no CodeRabbit review, no comment, and no
CodeRabbitstatus, while every human PR that day got one within minutes. Asked directly, CodeRabbit answered #56 in under three minutes, so the capability is plainly there.But GitHub ran a critical incident that day, 13:40:03Z to 21:15:46Z, with Webhooks among the affected components alongside Pull Requests, API Requests and Actions. A dropped
pull_requestwebhook produces exactly that silence, where a rate limit would have posted a banner. So the observation is unusable and has to be repeated on a clean day.Why this change is what unblocks the retest
Repeating it needs a bot PR to exist, and the weekly window is what prevents one: branch creation is only permitted between midnight and 7am on a Monday, and it is now Monday evening in Toronto, so the next natural opportunity is a week out. checkov 3.3.11 is already waiting behind the cooling period and clears it on the 20th.
Nothing else about the policy moves.
minimumReleaseAgestill holds every update for seven days, andprConcurrentLimitandprHourlyLimitstill bound how much arrives at once.Worth weighing before restoring it
The window costs up to seven days on top of the seven the cooling period already imposes, so a fix can be a fortnight old before it lands. It existed to give a person one sitting a week to work through the batch, and nothing is worked through by hand any more.