Copilot code review adds an enterprise-wide default review effort, and gives every plan the personal settings page
GitHub made a dedicated Copilot code review settings page available on every Copilot plan, and added an enterprise-wide default review effort setting that applies across every organisation-owned repository.
Why it mattersAn admin can now enforce one review depth across a whole enterprise without touching each repository, and Business and Enterprise users can finally set their own automatic-review behaviour instead of accepting the plan default.
A team on Copilot Business or Copilot Enterprise has, until this week, had no way to set its own automatic Copilot code review behaviour: the personal settings page for that only existed on the consumer Pro, Pro+ and Max plans. GitHub closed that gap on 2026-09-23 with a change now generally available.
The GitHub changelog names two things now GA. A dedicated Copilot code review settings page for automatic review and default review effort is now available on every Copilot plan, including Copilot Business and Copilot Enterprise. An enterprise-wide default review effort setting is also available for organisation-owned repositories.
The per-user page, on every plan
Under profile Copilot settings, a dedicated code review page under Copilot is now available across all plans. From that page, per the changelog, a user can turn on automatic reviews from Copilot, which trigger when the user creates a pull request, coauthors one, or moves one out of draft state. Automatic review for new pushes and for draft pull requests is a separate toggle. The default review effort is a separate setting again, shown today as Lite or Balanced, and applies to reviews the user requests, including reviews that were configured to fire automatically.
The change that Business and Enterprise plan users will notice first is the split into three toggles: automatic review, automatic review on new pushes and drafts, and default effort. Before this, the plan's single automatic-review switch did not distinguish drafts or pushes.
When a review is requested by hand from the pull request page under Reviewers, a different effort can still be selected before the request goes in, so the personal default is a default rather than a lock.
The enterprise-wide default
The second change is aimed at an admin. Authorised enterprise administrators can now set one default review effort for the whole enterprise, chosen from Lite, Balanced, or the GitHub default. That default applies to organisation-owned repositories through inheritance.
Organisations and individual repositories can still set their own overrides on top of the enterprise default. The enterprise-wide setting is the value that applies when nothing lower down changes it.
For a large org that had to negotiate consistent review behaviour across every team by hand, the setting removes the negotiation. For a smaller team, the same setting is where a platform group can set the review policy once and stop revisiting it per repository.
What this is not
The changelog is a configuration release, not a new capability inside the reviewer itself. There is no new model, no new inline suggestion category, no change to what a Copilot review looks like on the pull request. What changed is who can turn its behaviour on and off, and where the default lives.
That is the kind of change a team notices next Monday, not today: an admin can now flip one switch and see the same review effort across ten repositories that used to differ.
Source
- More ways to request and configure Copilot code reviews, GitHub Changelog, 2026-09-23
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
