Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Small-team tasks

Decide whether Copilot should approve PRs

Written November 2, 2026

Copilot approvals on pull requests are generally available and off by default. Turning them on means an agent approves — decide what a human still checks.

Audience: Team lead deciding whether an agent should approve pull requests · Stack: A GitHub repo with pull requests, Copilot code review enabled · Tool: GitHub Copilot code review approvals

What changed

On 28 October 2026, GitHub made Copilot approvals on pull requests generally available. Approvals had previously been available in public preview. They are available on Copilot Pro, Pro+, Max, Business, and Enterprise plans, per the changelog. Approvals are off by default. Nothing about a repository changes until an administrator turns them on, at the enterprise, organization, or repository level.

Every Copilot code review includes an approval assessment in the pull request overview comment, stating whether Copilot considers the pull request ready to merge. On its own, that assessment does not count toward merge requirements. When approvals are turned on, Copilot can submit an approving review, and that approval counts toward the repository's required approvals, as the usage documentation puts it, the same way a teammate's approval would. A review and an approval are different things: a review is advice with comments, an approval is a vote that can satisfy a merge rule. This page is about the vote, not the advice. The review itself is covered in the pull request review playbook.

How approvals work

Copilot's approval behaves like a human reviewer's approval. If new commits are pushed after Copilot approves, the approval is dismissed, and a fresh review can be requested for a fresh approval, according to the changelog. The approval assessment builds on the findings from the review itself: the same review that produced the comments produces the conclusion that the pull request is ready. An approval therefore adds no second check beyond the review. If the review missed an issue, the approval rests on the same missed issue.

Approvals are configured at three levels, and each level can narrow what the level below it may do. GitHub's configuration documentation sets out the controls. At the enterprise level, the policy for allowing Copilot to approve pull requests is Disabled everywhere by default; the alternatives are letting organizations decide or enabling it for selected organizations. At the organization level, the setting for counting Copilot approvals toward merge requirements offers four choices: Enabled everywhere, Let repositories decide, Enable for selected repositories, or Disabled everywhere. At the repository level, under Settings, then Copilot, then Code review, the Auto-approval section has two separate toggles: Allow Copilot to approve pull requests, and Allow Copilot approvals to count toward merge requirements. Check both toggles, not just the first. The first lets Copilot submit approving reviews; the second is what lets those approvals satisfy a merge rule.

Repository administrators can also limit approvals by file path. The documentation allows up to 15 globs, one per line, and approvals count toward merge requirements only on pull requests where every changed file matches one of the globs. Leave the field blank and approvals count for all files. A path limit is the main way to keep an approval from reaching code the team has not agreed an agent may sign off.

Strengths

Weaknesses and limits

What to do about it

  1. Start with the assessment, not the approval. Leave approvals off and read the approval assessment in the overview comment on real pull requests for a few weeks. Note where you agree with it and where you do not. If the assessment regularly disagrees with your call, the approval built on the same findings is not ready to count.
  2. If you turn approvals on, start narrow. Enable them on one repository, with file-path globs covering a small, low-risk area, for example documentation files only. Confirm both repository toggles are set the way you intend, and confirm the organization and enterprise settings above the repository actually permit approvals there. A repository toggle that a higher level has disabled does nothing.
  3. Write the remainder rule before the first counted approval. Write down what a human still checks on every pull request Copilot approves: intent and design, whether the change solves the right problem, test coverage, and anything outside the approved file paths. Put the rule where reviewers see it, and treat a merge that followed the rule as normal and a merge that skipped it as a process failure, even if the change itself was fine.
  4. Run one pull request through the full cycle. Request a review on a pull request in the scoped repository, watch the assessment and the approval, push a new commit, and confirm the approval is dismissed. Then re-request the review. Do this once, on a real pull request, before the team relies on approvals. If the dismissal does not happen as documented, stop and check the settings rather than working around it.
  5. Recheck the settings when the levels above change. An organization or enterprise policy change can widen or narrow what a repository may do. After any such change, re-read the repository's Auto-approval section and confirm the toggles and globs still say what the team decided.

Limits of this evaluation

Related playbooks

Sources

Back to: Small-team playbooks hub · Skills index

Also: Review a pull request with a coding agent · Triage issues with a read-only agent · Decide whether Copilot's assisted permissions should approve anything for you