docs: record #1217 prlanded merge and the confirmed #082 mitigation#1233
Conversation
PR #1217 squash-merged to main as 20300bb with PR required green and post-merge push CI green. Content verified on main: canRestoreFocusTo at both restore call sites, bounded reclaims, the event-driven settle window and no setInterval. #82 previously recorded racing the sync bot as the only workaround. Applying skip-branch-sync first stops the re-sync loop outright, which is what let #1217 hold a green head long enough to merge.
|
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 reached
Next review available in: 42 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ 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 |
Summary
Docs-only closing record for PR #1217, which squash-merged to
mainas20300bb9.docs/branch-review-ledger.md: head65f7580c→ squash20300bb9, with the landing evidence.#082indocs/outstanding-issues.md. It recorded racing the sync bot as the only workaround; applyingskip-branch-syncfirst stops the re-sync loop outright, which is what let fix(ui): harden Sheet focus handling #1217 hold a green head long enough to merge. The underlying fix (the repository Actions approval setting) is unchanged and still open.Landing evidence for #1217
gh pr viewstateMERGED, squash20300bb9, remote feature branch deleted by the merge.src/testsagainstorigin/mainis empty.sheet-focus.tsonmaincarriescanRestoreFocusTo,MAX_CONSECUTIVE_RECLAIMS, the event-driven settle window, and nosetInterval;sheet.tsxrestores throughcanRestoreFocusToat both call sites.PR requiredSUCCESS (Static, Safety and config, Unit coverage, Build, Production UI, Advisory UI). Post-merge push CI on20300bb9SUCCESS (CI, Docker image build, SAST, Secret Scan).pull_request_targetPR Policy run cancelled by its own successor, which reported SUCCESS.Verification
npm run check:branch-review-ledger— 928 records, union merge active, no conflict markers or duplicatesnpx prettier --check docs/clean (the#082wording was kept inside the existing column width so the table does not realign)Risk and rollout