chore(ledger): record Run PR sweep reviews for 12 open PRs - #2146
Conversation
Records the "Run PR" sweep review of every open PR that needed no product-code push of its own (dependency-bump PRs and doc/mockup PRs that were already clean or only needed a main sync): #2010, #2011, #2012, #2131, #2134, #2135, #2137, #2139, #2140, #2141, #2142, #2143. Three PRs surfaced real, non-mechanical problems left for human review rather than guessed at: - #2140: branch shares no common git ancestor with main - #2141: duplicates already-merged PR #2109's first commit - #2142: intentional archive PR, conflicts with main by design and needs its Clinical Governance Preflight checklist completed PR #2132's own sweep review record was already pushed directly to that PR's branch as part of its own commit, so it isn't duplicated here.
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in:8 minutes Limit details: You’ve used the included review currently available. Your 101 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. 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 within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (12)
Comment |
Summary
main(unrelated histories) — needs investigation/re-creation.mainby design, and its Clinical Governance Preflight checklist is unchecked in the PR body.Verification
npm run check:branch-review-ledger—Branch review ledger guard passed: 880 live table records + 1206 archived + 380 immutablenpx prettier --check docs/branch-review-records/*.record.md— cleanNot run: lint, typecheck, unit tests, build — diff is 12 new immutable ledger record files only, no source/config/test changes, so none of those gates has a failure path here.
Risk and rollout
Generated by Claude Code