Auto-Approve Low-Risk PRs

​

How Auto-Approve Works

1. Flawless Review Rating: The review achieves a 5/5 Confidence Score (Production ready) with zero critical or high-severity findings.
2. Within Maximum Risk Cap: The assessed risk profile of the changes does not exceed your configured risk threshold.
3. Satisfies Approval Guidelines: The diff complies with your team’s natural-language auto-approval instructions.

​

Configuring Auto-Approve in Blame

​

1. Enable Auto-Approve (auto_approve_prs)

• Enabled: Blame evaluates eligible PRs for automatic approval.
• Disabled (Default): Blame only posts informational reviews and check runs without issuing approvals.

​

2. Maximum Risk Level (auto_approve_max_risk)

​

Custom Approval Instructions

​

Recommended Instruction Templates

​

Scenario A: Documentation & Test Additions Only

Only auto-approve if the diff is restricted to:
1. Markdown files (`.md`, `.mdx`), documentation folders (`docs/**`), or repository READMEs.
2. Test files (`*.test.ts`, `*.spec.ts`, `tests/**`) with no modifications to source logic.

Do NOT auto-approve if any file in `src/`, `lib/`, or package manifests is modified.

​

Scenario B: Dependency & Automated Bot Updates

Auto-approve dependency bump PRs (e.g. from Dependabot or Renovate) only if:
- All CI test suites pass.
- No breaking major version changes are introduced.
- No public API signatures are modified.

​

Scenario C: Isolated Frontend Styling & Content

Allow auto-approval for CSS, Tailwind classes, and static copy updates in `app/(marketing)/**`.
Never auto-approve modifications in `backend/`, `api/`, or authentication middleware.

​

Safety Controls & Guardrails

• Draft PR Exclusions: Auto-approve evaluates pull requests only when they are marked Ready for review (unless draft reviews are explicitly enabled).
• Branch Protection Compliance: When combined with GitHub Status Checks, a PR will still require all required CI workflows and status checks to pass before merging.
• Immediate Invalidation on New Commits: If a developer pushes new commits to an approved PR, Blame re-evaluates the entire diff and invalidates the previous approval if new issues or risks are introduced.

​

Related Documentation

• CI/CD Quality Gates & Status Checks — Enforcing status check rules on pull requests.
• Configuring Review Strictness & Customization — Calibrating review depth and comment visibility.
• Review Architecture & Anatomy — Complete anatomy of Blame review comments.