@github: 84% of a PR’s open-to-merge lifecycle is spent waiting for approval. Once it gets the green light, it takes a median of…
Summary
GitHub Copilot now can approve pull requests after code review, aiming to reduce merge wait times by automating the approval process.
View Cached Full Text
Cached at: 09/10/26, 08:53 AM
84% of a PR’s open-to-merge lifecycle is spent waiting for approval. Once it gets the green light, it takes a median of 10 minutes to merge.
Instead of waiting for someone to sign off, you can now get an approval as soon as Copilot reviews your pull request. https://github.blog/changelog/2026-09-01-copilot-code-review-can-now-approve-pull-requests/…
Copilot code review can now approve pull requests
Source: https://github.blog/changelog/2026-09-01-copilot-code-review-can-now-approve-pull-requests/ Copilot now tells you when a pull request is ready to approve, and admins can authorize it to sign off on approval. The ability for Copilot to approve is off by default and configurable at the enterprise, organization, and repository level. The approval assessments will now appear as a part of the overview comment in every Copilot review. This feature is available in public preview to GitHub Copilot Pro, Pro+, Max, Business, and Enterprise plans.
✅ Approval assessments
Every Copilot code review now includes an approval assessment in the overview comment. The assessment signals whether Copilot considers the pull request ready to approve, giving you an at-a-glance read on its judgment alongside its detailed comments.
An approval assessment alone does not count toward merge requirements. Copilot’s determination is surfaced so you can decide how to act on it.
⚙️ Turning on approvals
By default, Copilot will not approve pull requests. When enabled, Copilot can submit an approval that counts toward the repository’s required-approvals rule. If new commits are pushed after Copilot approves, its approval is dismissed just like a human reviewer’s, and you can request a new review from Copilot to get a fresh approval.
Admins control this behavior at three levels:
- **Enterprise:**Admins can leave approvals off for the whole enterprise or let organizations decide.
- **Organization:**Admins can turn approvals on org-wide, let repository admins decide, enable it for specific repositories, or turn it off org-wide.
- **Repository:**Admins can turn approvals on or off, and choose which file paths Copilot is allowed to approve.
To learn more about configuring approvals for your enterprise, organization, or repository, see theCopilot code review documentation.
Similar Articles
Microsoft paper shows GitHub Copilot increases productivity 40%
A Microsoft study using 43 weeks of data from 16,223 engineers found that GitHub Copilot increases pull request completion by 40.5% when holding development effort constant.
@github: Pull requests are easier to open than ever, but every review still takes human effort. Introducing pull request limits:…
GitHub introduces pull request limits, allowing maintainers to cap open PRs from contributors without write access, with a bypass list for trusted contributors.
@github: Medium-depth reviews are now in public preview for GitHub Copilot code review. Increase the effort level from low to me…
GitHub Copilot's code review feature now supports medium-depth reviews in public preview, allowing users to increase the effort level for more thorough analysis by a higher-reasoning model.
GitHub turns Microsoft Teams discussions into shared Copilot agent sessions
GitHub's new Microsoft Teams integration enables shared Copilot agent sessions for collaborative AI-assisted work with human approval gates for pull requests.
@github: Every context switch has a cost: new window, new branch, "wait, where was I?" The GitHub Copilot app keeps the whole lo…
GitHub promotes its Copilot app as a tool that reduces context switches by keeping the entire development workflow from issue to merge in one place.