Skip to main content
Disabled by default. Enable per repo in Settings → Repos → Approvability.
Approvability

​
How It Works

When a PR is opened or updated, Macroscope runs two checks. Both must pass for auto-approval. If either fails, the PR can still be approved manually.

​
1. Eligibility

Is this PR a good candidate for auto-approval? Macroscope evaluates the changes, code ownership, git blame history, and the author’s role. If your repo has a CODEOWNERS file, Macroscope factors in the author’s relationship to changed files.
  • Typically eligible: docs, tests, code behind feature flags, simple bug fixes, copy changes.
  • Not eligible: large refactors, schema changes, security/auth/billing code, breaking changes.

​
2. Correctness

Did the PR pass Macroscope’s code review with zero issues flagged?
Results appear as Macroscope - Approvability Check in the Checks tab and as a PR comment with detailed reasoning. Approvability

​
Custom Eligibility Rules

Add a macroscope_approvability.md file to your repo root to define rules on top of the defaults: 
If a PR changes files in any of the following paths, DO NOT auto-approve:
- services/auth
- services/billing
- targets/auth

​
Setup

  1. Enable Approvability in Settings → Repos.
  2. (Recommended) Add a CODEOWNERS file to your repo.
  3. (Optional) Add a macroscope_approvability.md file with custom eligibility rules.
Macroscope cannot approve its own PRs.