GitHub Copilot Code Review Can Now Approve Pull Requests

Developer Tools · GitHub Copilot

GitHub Changelog  |  Entry published early September 2026

GitHub has published a changelog entry titled "Copilot code review can now approve pull requests," marking a significant shift in how the company's automated code-review feature behaves. Since Copilot code review launched, GitHub's own documentation has been unambiguous on one point: Copilot "always leaves a 'Comment' review, not an 'Approve' review or a 'Request changes' review," specifically so that its feedback would never count toward required approvals or block a pull request from merging. The new changelog entry indicates that restriction is changing.

What changed, based on prior documented behavior

Until this update, GitHub's own support documentation — mirrored in Microsoft's Azure DevOps documentation for Copilot code review — was explicit and consistent: Copilot's reviews were comment-only by design. As GitHub's docs previously put it, "Copilot always leaves a 'Comment' review, not an 'Approve' review or a 'Request changes' review. This means that Copilot's reviews do not count toward required approvals for the pull request, and Copilot's reviews will not block merging changes." A GitHub community discussion thread from mid-2025 confirmed the same limitation directly from GitHub staff, noting that teams wanting automated approvals had to build their own GitHub Actions workflows to do so, since "Copilot itself does not have this capability."

The new changelog entry's headline — appearing consistently across GitHub's changelog index, its tag-filtered Copilot views, and multiple related changelog posts published around the same period — indicates that limitation has now been lifted, at least in some capacity.

Part of a broader review overhaul

The approval change lands amid a string of upgrades to Copilot code review over the summer. In late July 2026, GitHub made agent skills and Model Context Protocol (MCP) support generally available for the feature, allowing Copilot's reviews to pull in a team's internal tools, coding standards, and third-party context — like issue trackers and documentation systems — directly into its analysis, rather than judging a diff in isolation. In June, GitHub introduced a "medium" analysis tier that routes more complex pull requests to a higher-reasoning model, and gave organizations more granular control over which Actions workflows and compute environments power reviews. Most recently, an August 27 update expanded Copilot's coverage to bot-authored pull requests — including those from Copilot's own cloud coding agent — and very large pull requests it previously couldn't handle, while also letting developers record a reason when resolving a Copilot review comment.

Taken together, the pattern is one of GitHub steadily moving Copilot code review from a supplementary commenting tool toward something closer to a full participant in the review process — culminating, per the new changelog headline, in the ability to actually approve changes.

Why the change matters

The distinction between "commenting" and "approving" has real teeth in GitHub's permission model. Repositories with branch protection rules can require a set number of approving reviews before a pull request is mergeable, and — under the old behavior — no volume of Copilot commentary could ever satisfy that requirement, nor could it block a merge the way a human "Request changes" review can. If Copilot can now issue genuine approvals, it raises immediate practical questions for engineering teams: whether Copilot approvals will be configurable to count toward required-reviewer policies, what conditions or confidence thresholds might govern when Copilot chooses to approve versus simply comment, and how organizations concerned about fully automated merges will want to configure the feature via policy controls, which GitHub has used for related Copilot settings in the past.

What we know vs. what's still unclear

Confirmed	Unclear from available reporting
GitHub published a changelog entry titled "Copilot code review can now approve pull requests"	Exact date of publication (appears to be early September 2026, alongside related Copilot changelog entries)
Prior GitHub documentation confirmed Copilot reviews were comment-only	Whether Copilot approvals count toward required-reviewer branch protection rules
The change follows several 2026 upgrades to Copilot code review (agent skills, MCP, effort tiers, bot PR support)	Whether the new approval capability is on by default or requires explicit configuration
GitHub has historically gated similar changes behind organization/repository-level policy settings	Any conditions or thresholds governing when Copilot chooses to approve rather than comment

What to do next

Engineering teams using Copilot code review — particularly those with branch protection rules requiring a minimum number of approvals — should review GitHub's official changelog and documentation directly before assuming this capability is active on their repositories, given that the specific mechanics weren't available for this report. GitHub has a track record of rolling out Copilot behavior changes behind opt-in policies at the organization or enterprise level, so it would be consistent with past practice for this to require explicit enablement rather than applying automatically to every repository with Copilot code review turned on.

Sources

• GitHub Changelog — Main index (referencing "Copilot code review can now approve pull requests")
• GitHub Changelog — "GitHub Copilot in VS Code, August 2026 releases"
• GitHub Changelog — "Copilot code review: Resolution reasons and expanded capabilities"
• GitHub Changelog — "Copilot code review: Agent skills and MCP now generally available"
• GitHub Changelog — "Shape Copilot code review around your team"
• GitHub Changelog — "Upcoming changes to GitHub Copilot policies and billing"
• GitHub Docs — "Using GitHub Copilot code review" (documents prior comment-only behavior)
• Microsoft Learn — "Get started with Copilot code review for pull requests - Azure Repos"
• Real Python — "How to Use GitHub Copilot Code Review in Pull Requests"
• GitHub Community Discussion — "Can copilot approve pull requests?"

Also Read: AI Industry Slowdown Article

SPONSORED ADS