coderabbit-incident-runbook

# CodeRabbit Incident Runbook ## Overview Rapid incident response procedures when CodeRabbit stops reviewing PRs, blocks merges, or behaves incorrectly. Since CodeRabbit is a managed SaaS service, incidents fall into two categories: (1) CodeRabbit service outage (check their status page), or (2) local configuration/permission issues (fix on your side). ## Severity Levels | Level | Symptom | Response Time | Action | |-------|---------|---------------|--------| | P1 | PRs blocked, cannot merge | Immediate | Bypass check, notify team | | P2 | Reviews not posting | < 1 hour | Diagnose installation | | P3 | Reviews delayed (> 15 min) | < 4 hours | Check service status | | P4 | Incorrect reviews | Next business day | Tune configuration | ## Instructions ### Step 1: Quick Triage (2 Minutes) ```bash set -euo pipefail echo "=== CodeRabbit Quick Triage ===" # 1. Check CodeRabbit status page echo "--- Service Status ---" STATUS=$(curl -sf https://status.coderabbit.ai 2>/dev/null && echo "REACHABLE" || echo "UNREACHABLE") echo "Status page: $STATUS" echo "Check manually: https://status.coderabbit.ai" echo "" echo "--- Decision ---" echo "If status.coderabbit.ai shows an incident:" echo " → CodeRabbit-side issue. Wait for resolution. Use bypass if blocking." echo "" echo "If status page is green:" echo " → Local issue. Check installation, config, permissions." ``` ### Step 2: P1 Emergency -- PRs Blocked ```bash set -euo pipefail OWNER="${1:-your-org}" REPO="${2:-your-repo}" ech...