docs: recover governance incident runbook#706
Conversation
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
Warning Review limit reached
Next review available in: 20 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 (3)
📝 WalkthroughWalkthroughAdded governance incident-response runbooks, linked them from the documentation index, and recorded the related historical branch cleanup in the review ledger. ChangesGovernance documentation
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/governance-incident-runbooks.md`:
- Around line 24-27: Update the incident runbook step covering raw query/answer
persistence and provider-response storage to fail closed: explicitly disable
either path if found enabled, then verify both settings are off before
proceeding to cache and telemetry retention assessment. Keep the existing
escalation guidance unchanged.
In `@docs/README.md`:
- Line 47: Update the governance-incident-runbooks.md index entry in
docs/README.md to mention answer-pipeline rollback alongside the existing
incident categories, preserving the link and current description.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 32b19124-9350-47ad-a37e-c4528ee38166
📒 Files selected for processing (3)
docs/README.mddocs/branch-review-ledger.mddocs/governance-incident-runbooks.md
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 300acbacc4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fec0aa6367
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
1 participant
Summary
Why
The historical branch mixed obsolete implementation work with one durable operational artifact. Recovering only the runbook preserves useful governance guidance without reintroducing superseded code.
Files
docs/governance-incident-runbooks.mddocs/README.mddocs/branch-review-ledger.mdVerification
npx prettier --check docs/README.md docs/branch-review-ledger.md docs/governance-incident-runbooks.md— passednpm run docs:check-links— passed; 824 references resolvednpm run docs:check-scripts— passed; 264 npm script references resolvedgit diff --check— passedChecks not run
No application, browser, clinical, Supabase, or provider-backed checks were run because this is a documentation-only recovery.
Risk
Low. The change adds operator documentation and ledger metadata only; it does not alter runtime behavior.
Summary by CodeRabbit