CodeRabbit Incident Runbook

Overview

Contain impact while preserving independent security and CI. Separate provider health, service health, config, permissions, limits, and harmful output.

Prerequisites

• Identify the CodeRabbit organization, Git provider, repository, plan, and accountable owner.
• Read references/official-docs.md and re-check any time-sensitive contract before execution.
• Use synthetic or read-only evidence until the approval boundary is satisfied.
• Preserve the repository's independent CI, security, and human-review requirements.

Current Contract

• CodeRabbit can fail independently from repository CI.
• Limits and exclusions can resemble an outage.
• Bypass authority belongs to repository governance.
• Status evidence needs timestamps and local corroboration.