issues: add #082 — bot branch-sync heads leave required checks unapproved

[BigSimmo]

Ledger-only. Records the merge friction seen on PR #1220 as a tracked open item instead of leaving it as narrative inside one branch-review row.

The github-actions[bot] sync merge updates open PR branches every 10–20 minutes, and every bot-authored head produces action_required runs for CI, SAST and Secret Scan. Those runs never execute without manual approval, so the three required checks never report and the PR cannot merge — #1220 was blocked through five successive syncs (e927cc3c, e74ce083, 84a224ba, 54bea70b, 0ab9e331), and both a normal merge and --admin were refused. Heads pushed by an agent or a human still run normally, which is the only current workaround: push an own-authored head and merge on green before the next sync.

The row lists three candidate fixes (allow the sync bot in the repository Actions approval setting, push the sync with a token whose runs auto-execute, or drop auto-sync and let authors update their own branches) and two stop rules: do not widen approval settings for fork or untrusted actors, and do not clear the block by bypassing required checks.

Kept out of the recommended execution queue, consistent with #080; it is an open item to decide on, not scheduled work. issues:next-id bumped to 083.

RAG impact: no retrieval behaviour change — documentation ledger only.

Checks: npm run format:changed.

  

[chatgpt-codex-connector]

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.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 12 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: 76617650-c8c5-44f2-a459-2a48228efed2

📥 Commits

Reviewing files that changed from the base of the PR and between 584b804 and d2f08d5.

📒 Files selected for processing (1)

• docs/outstanding-issues.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/issues-082-ci-approval-friction-6273

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[supabase]

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 ↗︎.