Skip to content

docs: record #1217 prlanded merge and the confirmed #082 mitigation#1233

Merged
cursor[bot] merged 1 commit into
mainfrom
cursor/ledger-1217-prlanded-c6d3
Jul 25, 2026
Merged

docs: record #1217 prlanded merge and the confirmed #082 mitigation#1233
cursor[bot] merged 1 commit into
mainfrom
cursor/ledger-1217-prlanded-c6d3

Conversation

@BigSimmo

Copy link
Copy Markdown
Owner

Summary

Docs-only closing record for PR #1217, which squash-merged to main as 20300bb9.

  • Appends the prlanded row to docs/branch-review-ledger.md: head 65f7580c → squash 20300bb9, with the landing evidence.
  • Updates #082 in docs/outstanding-issues.md. It recorded racing the sync bot as the only workaround; applying skip-branch-sync first 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 view state MERGED, squash 20300bb9, remote feature branch deleted by the merge.
  • Two-dot content diff of src/tests against origin/main is empty.
  • sheet-focus.ts on main carries canRestoreFocusTo, MAX_CONSECUTIVE_RECLAIMS, the event-driven settle window, and no setInterval; sheet.tsx restores through canRestoreFocusTo at both call sites.
  • Hosted PR required SUCCESS (Static, Safety and config, Unit coverage, Build, Production UI, Advisory UI). Post-merge push CI on 20300bb9 SUCCESS (CI, Docker image build, SAST, Secret Scan).
  • The single red entry in the fix(ui): harden Sheet focus handling #1217 rollup was a pull_request_target PR 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 duplicates
  • npx prettier --check docs/ clean (the #082 wording was kept inside the existing column width so the table does not realign)
  • No provider-backed checks; no source, test, or config changes

Risk and rollout

  • Risk: none — documentation only.
  • Rollback: revert this commit.
  • Provider or production effects: None
Open in Web Open in Cursor 

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.
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@supabase

supabase Bot commented Jul 25, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@coderabbitai

coderabbitai Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: b5b69a13-77ed-4208-9b70-f323e9d61daf

📥 Commits

Reviewing files that changed from the base of the PR and between 20300bb and b5e080a.

📒 Files selected for processing (2)
  • docs/branch-review-ledger.md
  • docs/outstanding-issues.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cursor/ledger-1217-prlanded-c6d3

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@cursor
cursor Bot merged commit 0122f05 into main Jul 25, 2026
18 checks passed
@cursor
cursor Bot deleted the cursor/ledger-1217-prlanded-c6d3 branch July 25, 2026 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants