← Back to BlogCode Review

Can Copilot Approve Pull Requests? Yes, If You Turn It On

GitHub made Copilot approvals GA on October 28 and put Agent Merge in pull requests. What counts as a review, and how to keep a human in the path.

Yes. GitHub made Copilot approvals generally available on October 28, 2026, so Copilot code review can now submit an approving review that counts toward your repository's required approvals. It is off by default, which means nothing changes until an administrator switches it on at the enterprise, organization or repository level. The same day, Agent Merge arrived inside pull requests on GitHub: Copilot watches a pull request and fixes the failing Actions workflows and merge conflicts that block it.

Sources: GitHub Changelog: Copilot code review, Merge with confidence with Max and approvals (Oct 28, 2026), GitHub Changelog: Agent Merge watches and fixes pull requests in the cloud (Oct 28, 2026)

Combine the two with auto-merge and a pull request can be merged without a person approving it, if your rules count Copilot's approval toward the requirement. That outcome comes from your settings, and they live in three places. This post covers what shipped, the switches that decide whether a Copilot approval counts, three gaps a green check can hide, and a short rule set that keeps a human in the path where a bad merge costs the most.

Disclosure: we build TLM Forge, a process layer for Claude Code, so weigh the product section accordingly. Most of this post is about GitHub's settings and applies with or without us.

What GitHub shipped, and when

Every item below comes from GitHub's own changelog. Approvals are available on Copilot Pro, Pro+, Max, Business and Enterprise plans. Agent Merge in the cloud needs a paid Copilot plan and is subject to organization and enterprise policies.

Sources: GitHub Changelog: Copilot code review, Merge with confidence with Max and approvals (Oct 28, 2026), GitHub Changelog: Agent Merge watches and fixes pull requests in the cloud (Oct 28, 2026)

  • September 1, 2026: every Copilot code review gained an approval assessment in its overview comment, and approvals arrived in public preview. The entry says an assessment alone does not count toward merge requirements.
  • October 28, 2026: approvals became generally available. The same entry introduced Max, a third review effort level in public preview that runs several independent review agents across models from different providers.
  • October 28, 2026: Agent Merge came to pull requests on GitHub through a Watch and fix button in the merge box. It was already available in the GitHub Copilot app and Visual Studio Code.
  • November 6, 2026: the weekly release notes say you can set up Agent Merge from a pull request in the Copilot app so that Copilot merges it when it is ready. They add: "It now stays enabled while required checks or rules are pending."

GitHub's stated aim is a high-confidence approval with less waiting. The entry says the pairing lets you "merge with confidence and spend less time waiting on review." It suggests pairing Max with approvals on the repositories where a missed issue costs the most, and it does not say approvals require Max. GitHub also says Max takes longer and uses more AI credits than Lite or Balanced. For GitHub's own numbers on an earlier ensemble change at the Lite level, which is separate from Max, see GitHub Says Its AI Code Reviewer Got 47% Better.

Sources: GitHub Changelog: Copilot code review, Merge with confidence with Max and approvals (Oct 28, 2026)

Does a Copilot approval count? The switches that decide it

By default, no. GitHub's documentation says Copilot's reviews do not count toward required approvals. When approvals are enabled in repository, organization and enterprise settings, Copilot can submit an approving review that satisfies the repository's required-approval rule "the same way a teammate's approval would." Whether yours does depends on three levels.

Sources: GitHub Docs: GitHub Copilot code review, GitHub Docs: Configuring code review by GitHub Copilot

LevelWhere the setting livesOptions
EnterpriseAI controls, then Copilot, then Configure features & clients, then Copilot code review: "Allow Copilot to approve pull requests"Let organizations decide, Enable for selected organizations, or Disabled everywhere. Disabled everywhere is the default.
OrganizationSettings, then Copilot, then Code review: "Count Copilot approvals toward merge requirements" under ApprovalsEnabled everywhere, Let repositories decide, Enable for selected repositories, or Disabled everywhere.
RepositorySettings, then Copilot, then Code review: the Auto-approval sectionTwo toggles (allow Copilot to approve, and allow its approvals to count toward merge requirements) plus an optional list of file globs.

Two details are easy to miss. First, the repository has two toggles: one lets Copilot submit approving reviews, and the other lets those approvals satisfy approval requirements. Second, the file paths box limits counting. GitHub's settings page says to enter one glob per line, up to 15, to count approvals only on pull requests where every changed file matches one of the globs, and that a blank box counts approvals for all files. One changed file outside your list is enough to stop the approval counting on that pull request. The changelog describes the same box as the paths Copilot is allowed to approve, so use the settings page wording when you test.

Sources: GitHub Docs: Configuring code review by GitHub Copilot, GitHub Changelog: Copilot code review, Merge with confidence with Max and approvals (Oct 28, 2026)

A Copilot approval does not outlive a push. If new commits arrive after Copilot approves, the approval is dismissed and you can request a new review. Unless a ruleset or the author's own settings turn on Review new pushes, Copilot reviews a pull request once, so a later push does not trigger a fresh look by itself.

Sources: GitHub Changelog: Copilot code review, Merge with confidence with Max and approvals (Oct 28, 2026), GitHub Docs: GitHub Copilot code review

Agent Merge, approvals and auto-merge: how the pieces connect

GitHub's docs describe Agent Merge as part of Copilot in the cloud that "watches a pull request for blockers you choose and starts work automatically when it finds one." You pick Fix failed Actions workflows, Resolve merge conflicts, or both. The fixes run in a GitHub Actions-based development environment. Agent Merge does not support stacked pull requests or pull requests opened from a fork, and its AI credits are charged to the user who enables it for the pull request, not necessarily the author. In the Copilot app it can also address review comments, which the docs say is not supported in the cloud.

Sources: GitHub Docs: Getting pull requests ready to merge with Agent Merge, GitHub Docs: Managing issues and pull requests with the GitHub Copilot app

On GitHub, Agent Merge does not do the merging. The docs say it fixes blockers while auto-merge merges a pull request after all required reviews and status checks pass, and that "Enabling Agent Merge does not enable auto-merge." You can combine them. In the Copilot app, the docs say Agent Merge reads the pull request, fixes what blocks it and merges it as soon as GitHub allows.

Sources: GitHub Docs: Getting pull requests ready to merge with Agent Merge, GitHub Docs: Automatically merging a pull request, GitHub Docs: Managing issues and pull requests with the GitHub Copilot app

Read the pieces in order and a pipeline appears. Agent Merge makes changes to clear a blocker, and the pages we read do not say how it lands them. If they arrive as new commits, they dismiss an earlier Copilot approval. If Review new pushes is on, Copilot reviews again and may approve again. When the checks pass and the approval counts, auto-merge completes the merge. Most of these rules are documented on their own pages, but no page describes the whole chain. We have not run it end to end, so test it on a scratch repository before assuming it behaves this way in yours.

GitHub's docs state the intent clearly. Agent Merge "does not replace your review of the changes or the repository's merge requirements," and it "does not remove the need for human review." Those sentences describe how GitHub expects you to use the feature. What enforces a human is your rule set, and with Copilot approvals counting, a one-approval rule can be satisfied with no person approving.

Sources: GitHub Docs: Getting pull requests ready to merge with Agent Merge

Agent Merge is part of Copilot in the cloud, which makes it easy to over-read the guard rails GitHub documents for its cloud agent. Draft pull requests the cloud agent creates must be reviewed and merged by a human. It cannot mark them Ready for review, and it cannot approve or merge a pull request. By default, workflows do not run until its code is reviewed and a user with write access clicks Approve and run workflows, and the user who asked for the pull request cannot approve it. When it opens a pull request under its own app identity, the ruleset default adds one more required approval when the ruleset already requires at least one. Those lines describe the cloud agent's own pull requests. Copilot code review is a different feature, and approvals are its switch.

Sources: GitHub Docs: Risks and mitigations for GitHub Copilot cloud agent, GitHub Docs: Available rules for rulesets

The ruleset page gives an example of that extra approval: a ruleset that requires one approval then needs two approvals from people with write access. Whether a Copilot code review approval can fill one of those slots is not spelled out on the pages we read. Test that interplay before you rely on either reading.

Sources: GitHub Docs: Available rules for rulesets

Three gaps a green check can hide

1. Files Copilot code review does not read

GitHub documents a list of files that Copilot code review skips, and says it "will not consider the file when carrying out the review." The examples include package-lock.json, yarn.lock, requirements.txt, go.sum, Cargo.lock, tsconfig.json and build.gradle. Excluded patterns include **/*.lock, **/dist/**/*, **/vendor/**/*, **/generated/**/* and **/node_modules/**/*.

Sources: GitHub Docs: Files excluded from GitHub Copilot code review

The changelog says Copilot's approval assessment builds on the findings from its review. None of the pages we read says how the assessment treats a pull request that changes only excluded files, so do not assume the review examined anything there. Dependency pins and lockfile changes are changes a human should look at, so keep those paths outside your file allowlist and an approval cannot count on a pull request that changes them.

Sources: GitHub Changelog: Copilot code review, Merge with confidence with Max and approvals (Oct 28, 2026), GitHub Docs: Files excluded from GitHub Copilot code review

2. A fix that lands after the approval

Agent Merge makes changes to clear a blocker, and the docs ask you to review those changes. A Copilot approval is dismissed by new commits, which is the right behavior. GitHub's ruleset docs explain why it matters for any approval: if you are concerned about unapproved content being added to approved pull requests, "it is safer to dismiss stale reviews." Turn on Dismiss stale pull request approvals when new commits are pushed in the default-branch ruleset, and decide on purpose whether Review new pushes is on. Without Review new pushes, Copilot does not look at later pushes unless someone requests a review.

Sources: GitHub Docs: Available rules for rulesets, GitHub Docs: Getting pull requests ready to merge with Agent Merge, GitHub Docs: GitHub Copilot code review

3. Green check, same code

Fix failed Actions workflows is a job description, and an agent can finish it by changing the code or by changing what the check measures. We cover the second path for Claude Code in How to Stop Claude Code Changing Tests to Pass. The Agent Merge docs list the blockers it handles and the environment it runs in. They do not mention limits on which files it may change, and they tell you to review what Copilot changes and check the workflow results before merging. Treat Agent Merge's changes like changes from any other author, and read the diff of the test and workflow files first.

Sources: GitHub Docs: Getting pull requests ready to merge with Agent Merge

Rules that keep a human in the path

This is a starting set built only from controls GitHub documents. We have not applied it to a live repository, so try it on a scratch one first.

  • Approvals: keep Disabled everywhere as the enterprise policy until a team asks, then use Enable for selected organizations and, inside the organization, Enable for selected repositories. In repositories that opt in, switch on both Auto-approval toggles on purpose, and fill the file paths box with a low-risk allowlist, such as your docs folder, instead of leaving it blank. Blank counts approvals for all files.
  • Ruleset on the default branch: require a pull request, at least one approval, Dismiss stale pull request approvals when new commits are pushed, and the option that requires reviews from code owners. With that last option, any pull request that modifies content with a code owner must be approved by that code owner.
  • CODEOWNERS: name a human team for the paths a bad merge would hurt most. Owners must have write access, and the file must be on the pull request's base branch for owners to get review requests.
  • Auto-merge: it waits for all required reviews and status checks, so the code owner rule holds it until the owner approves. Check that auto-merge is enabled on the repository only where you want it.
  • Agent Merge: the Enable Agent Merge automatically for pull requests I create setting sits in each person's own Copilot settings, so ask who has it on. For sensitive repositories, check the repository's Enable automations Copilot policy, which the docs list as a prerequisite. Anyone with write access can disable it on a single pull request.

Example CODEOWNERS lines

  • /.github/ @your-org/platform covers workflows, the Copilot instruction files under .github and the CODEOWNERS file itself if it lives there.
  • package-lock.json @your-org/platform and go.sum @your-org/platform cover two of the lockfiles Copilot does not review.
  • *.lock @your-org/platform covers the lockfile pattern in the excluded list.

Replace @your-org/platform with a team that has write access, or the line assigns no owner. Order matters too: GitHub's example file notes that the last matching pattern takes the most precedence, so place these lines after any broader pattern such as *. GitHub's docs also say you need an owner for the CODEOWNERS file itself to protect a repository fully against unauthorized changes.

Sources: GitHub Docs: About code owners

One report: a user in GitHub's community discussion for the Agent Merge announcement asked, "How do I disable this? On repo, organization and/or enterprise level?" and said they could not find a setting for it. That is one report, posted on October 29. The docs we read name the Enable automations policy as a prerequisite and a per-pull-request disable. We did not test whether the policy hides the button.

Sources: GitHub Community discussion 211009, comment of Oct 29, 2026, GitHub Docs: Getting pull requests ready to merge with Agent Merge

Five checks on the settings you already have

  • Are the enterprise policy Allow Copilot to approve pull requests and the organization setting Count Copilot approvals toward merge requirements set to anything other than Disabled everywhere?
  • In each repository where it is on, are both Auto-approval toggles on, and is the file paths box blank?
  • How many approvals does the default-branch ruleset require? If the answer is one, a counting Copilot approval can satisfy it alone.
  • Is the code owner review requirement on, and does CODEOWNERS name a human team for dependency files, workflows and anything touching authentication or secrets?
  • Is auto-merge allowed on the repository, and does anyone have Agent Merge enabled by default in their Copilot settings?

When letting Copilot approve is a reasonable call

None of this argues against the feature. GitHub's pitch is less waiting on review, and for documentation or copy changes that trade can be reasonable, especially because the approval expires on the next push. The risk sits in the defaults you choose, not in the checkbox. For how to tier changes by risk before deciding which tier a bot may approve, see Approval Gates for High-Risk AI Code Changes. If you work under SOX or PCI-DSS, read AI Agents, SOX, and PCI-DSS Segregation of Duties before counting any bot approval toward a required review.

SetupWho approves a typical pull requestWhat can slip throughReasonable when
Approvals off (the default)A human reviewerNothing new. Copilot review is advice and does not count toward required approvals.Most repositories, and the right place to start.
On, file paths blankCopilot alone can satisfy a one-approval rule once its review judges the change readyAnything the review skips or misjudges, including lockfiles and other excluded files.A scratch or solo repository where you accept that risk.
On, path allowlist plus code ownersCopilot for pull requests where every file matches the allowlist; a named owner where owners are setA globs list that matches more than you meant, or paths wrongly labeled low risk.Teams with clear low-risk paths and an owner for everything else.
Agent Merge plus auto-mergeWhoever your rules require. Agent Merge fixes blockers and does not replace review.A fix that turns checks green by changing what the check tests.Routine blockers such as conflicts, with a human approval still required.

Where TLM Forge fits

TLM Forge works inside Claude Code, not inside GitHub's merge box. On Medium and Deep tasks it runs a final review wave of independent reviewer agents: code-reviewer and phase-auditor on Medium, with tester, red-team-reviewer and architect-reviewer added on Deep. CRITICAL and HIGH findings are fixed test-first, and a CRITICAL it cannot fix is brought to you. A commit hook blocks git commit, git push and gh pr merge when the code changed since that review.

The limits matter here. The hook matches the text of those three commands, so a click on the Merge button, GitHub's auto-merge and Copilot's approvals are outside it. The reviewers are LLM agents and can miss things. A required human approval has to live in your GitHub rules.

Frequently asked questions

01Can GitHub Copilot approve pull requests?

Yes, once an administrator turns it on. Copilot code review can submit an approving review, and GitHub made that generally available on October 28, 2026. It is off by default, and an approval assessment alone does not count toward merge requirements.

02Does a Copilot approval count as a required review?

Only if the settings at every level allow it. In a repository, one toggle lets Copilot submit approving reviews and another lets them satisfy approval requirements. Optional file globs, up to 15, restrict counting to pull requests where every changed file matches. New commits dismiss the approval.

03Does Agent Merge merge pull requests by itself?

On GitHub, Agent Merge fixes failing Actions workflows and merge conflicts, and auto-merge does the merging once required reviews and checks pass. In the Copilot app, GitHub says it merges the pull request as soon as GitHub allows.

04How do I stop Copilot from approving or merging my pull requests?

Keep the enterprise or organization approvals setting at Disabled everywhere. Where repositories decide, leave both Auto-approval toggles switched off. For Agent Merge, GitHub lists the Enable automations policy as a prerequisite, and anyone with write access can disable it on one pull request.

05How do I keep a human reviewer on AI-written pull requests?

Name a human team in CODEOWNERS for sensitive paths and require reviews from code owners in your ruleset. Limit Copilot counting to low-risk file globs, dismiss stale approvals on new commits, and keep those rules in GitHub, not in the agent.

Ship AI-written code you can trust

TLM Forge is the missing process layer for Claude Code: a spec audit, independent multi-agent review, enforced TDD, and an adversarial red-team gate.

Get TLM Forge