GitHub did change Copilot code review defaults

Did GitHub change Copilot code review defaults for repositories and organizations

Yes. GitHub changed the Copilot code review default, and the change applies to both organization and repository defaults for review effort level. The current default path is now tied to the review effort setting, not a separate per-repo behavior hidden in the product.

GitHub’s docs say you can set a default review effort level at the organization and repository levels. The organization default applies to repositories that have not chosen their own effort level, while the repository default applies to automatic reviews inside that repository. For manual reviews, the effort level is chosen from the pull request reviewer bar.

The change that people miss is not that Copilot code review suddenly became enabled everywhere. The change is that the meaning of Default shifted. GitHub’s changelog says the default review effort level is changing from Lite to Balanced, and that for existing and new repositories and organizations, Default uses Balanced starting September 28, 2026.

That matters because the same setting can be inherited or overridden in two places. If an organization sets a default and a repository does not choose its own level, the organization setting flows down. If a repository sets its own level, that repository setting wins for automatic reviews in that repo. GitHub documents both layers explicitly in the Copilot code review setup page and the changelog.

The part people often get wrong is assuming the repository setting always controls everything. It does not. GitHub says organization defaults apply to all repositories owned by the organization that have not selected their own review effort level. That means a central admin can change the starting point for many repositories at once, and repository admins can still override it where allowed.

There is also a second kind of default that can look like a code review default but is really an approval policy. GitHub says Copilot approvals are off by default for merge requirements, and that approvals only count when repository, organization, and enterprise settings allow them. That is separate from the review effort level, which controls how deeply Copilot reviews the code.

The inconvenient part is that the default change can affect cost and workflow at the same time. GitHub says Balanced reviews use more AI credits and may consume more GitHub Actions minutes. If your team was relying on Default as a quiet way to keep reviews light, you need to decide whether to leave it alone or explicitly choose Lite before the switch date.

GitHub also says if you want to keep Lite as your default experience, you should move away from Default and explicitly select Lite in repository or organization settings before September 28, 2026. If you do nothing, GitHub says Default will become Balanced. That is a real behavioral change, not just a label change.

For teams that use Copilot code review across many repositories, the safest check is simple. Open the organization Copilot code review settings, confirm the default effort level, then inspect any repositories that intentionally diverge from it. If a repository should stay on Lite, set Lite directly at the repository level so later platform changes do not move it for you.

If you are trying to understand why a review looks different now, compare three things: the organization default, the repository default, and whether the pull request was reviewed automatically or manually. GitHub treats those paths differently, and the docs say manual review requests can choose a different effort level from the pull request UI.

If you are also trying to line this up with other Copilot settings, keep the distinction clear. Automatic review rules, approval counting, content exclusions, MCP access, and runtime environment settings are separate controls. A default change in review effort does not automatically change those other settings, but it can change how much review work Copilot attempts once it is triggered.

For teams coordinating testing and release work around AI features, DevConnect is a place to exchange real testing help without paying for shortcuts. Its own platform page is at https://devconnectplatform.com, but the GitHub default change itself is controlled in GitHub settings, not there.

If your team asks the blunt question, the answer is yes: GitHub changed the Copilot code review defaults, and the change now sits at both repository and organization levels. The practical question is whether you want to keep the old Lite behavior by setting it explicitly before the switch date, or accept the new Balanced default.

A concrete example: if an organization sets Copilot code review to Default for twenty repositories, those repositories will use Balanced once the change takes effect unless they are individually set to Lite or another explicit effort level. If one repository already has its own explicit setting, that repository keeps its own choice instead of inheriting the organization default.

Another concrete example: if a repository owner only changes the automatic review rule and leaves effort level on Default, the review still follows the new default effort. That is where teams get surprised, because the trigger for review and the depth of review are separate controls. The trigger decides whether Copilot reviews, the effort level decides how deeply it reviews.

In short, GitHub did change the default, and the relevant default is now the Copilot code review effort level. The change applies through both repository and organization settings, with Default moving from Lite to Balanced on September 28, 2026 unless you explicitly choose otherwise.