GitHub Copilot Code Review: Max Effort Level and Approvals
GitHub CopilotGitHub added a Max review effort level (public preview) to Copilot code review, running several independent review agents across models from different providers and reconciling their findings with an aggregation agent. Copilot approvals are now generally available, so Copilot can approve a pull request and have that approval count toward required approvals. Max takes longer and uses more AI credits than Lite or Balanced.
Key Takeaways
- Max runs multiple review agents across models from different providers, then reconciles them with an aggregation agent to reduce blind spots.
- Copilot approvals are now generally available and count toward a repository's required approvals.
- A Copilot approval is dismissed automatically when new commits are pushed, matching human reviewer behavior.
- Max costs more time and AI credits than Lite or Balanced, so it suits risky changes such as authentication or shared libraries.
- Effort can be set per pull request, or as a default for a repo, org or enterprise, with admins able to cap the maximum level.
- Approvals are off by default, and repository admins can limit which file paths Copilot may approve.
Max: the deepest review Copilot offers
GitHub Copilot code review gained a third review effort level, Max, now in public preview alongside Lite and Balanced. It is aimed at riskier changes, such as edits to authentication logic or to a shared library that several services depend on. Max runs several independent review agents across models from different providers. Each model has its own strengths and blind spots, so combining them helps catch issues a single model might miss. An aggregation agent then reconciles the findings, resolves disagreements and double-checks accuracy before merging everything into a single review. The goal is the broadest coverage on critical issues while keeping noise low.
Because Max does more work on each review, it takes longer and uses more AI credits than Lite or Balanced, so it makes sense to reserve it for changes where a missed issue is expensive.
Approvals reach general availability
Copilot approvals, previously in public preview, are now generally available. Copilot code review acts as both reviewer and approver. Every review includes an approval assessment in the pull request overview comment that says whether Copilot considers the pull request ready to merge. When approvals are turned on, Copilot can approve the pull request, and that approval counts toward the repository's required approvals. It behaves like a human reviewer's approval: if new commits are pushed after Copilot approves, the approval is dismissed and a new review can be requested for a fresh approval.
Better reviews, better approvals
The approval assessment builds on the findings of the review itself, so pairing Max with approvals on high-stakes repositories means Copilot's sign-off reflects its most thorough analysis.
Configuring Max and approvals
Max can be selected for a single pull request from the Reviewers bar, or set as the default review effort for a repository, organization or enterprise, with each level able to override the one above it. Admins can optionally set a maximum effort level, and levels above it are unavailable in that scope. Approvals are off by default. Admins can turn them on at the enterprise, organization or repository level, and repository admins can restrict which file paths Copilot may approve. Both features are available on Copilot Pro, Pro+, Max, Business and Enterprise plans.