GitHub Reverses Automatic Copilot Code Reviews in Code Quality
GitHub CopilotGitHub reversed a default it shipped with GitHub Code Quality's July 20, 2026 general availability launch: enabling Code Quality on a repository no longer automatically adds GitHub Copilot as a pull request reviewer. The change disables the automatic review-request settings in the ruleset Code Quality previously created, restoring reviewer assignment as a deliberate choice for repository and organization owners, while leaving Copilot code review itself — and its billing — unchanged for anyone who re-enables it manually.
Key Takeaways
- GitHub Code Quality no longer auto-adds Copilot as a pull request reviewer when the product is enabled on a repository, reversing its July 20, 2026 GA-launch default.
- The reversal followed direct user feedback that reviewer assignment should be a deliberate choice, not an automatic side effect of enabling Code Quality.
- Three specific ruleset settings were disabled: automatic review requests on every PR, re-review on new pushes, and review requests on draft PRs.
- Any ruleset a team has already customized is left untouched — GitHub only modifies rulesets that still match what it originally created.
- Automatic Copilot code review can still be re-enabled manually at the repository or organization level via rulesets, and continues to bill against the team's Copilot plan.
- The change affects GitHub Enterprise Cloud and GitHub Team customers using Code Quality, without altering Copilot code review's underlying capability.
GitHub Reverses Automatic Copilot Code Reviews in Code Quality
GitHub has reversed a default behavior it shipped with GitHub Code Quality just weeks ago: enabling Code Quality on a repository no longer automatically adds GitHub Copilot as a pull request reviewer.
What Changed
When Code Quality reached general availability on July 20, 2026, turning it on for a repository silently created a ruleset named Code Quality Copilot review for default branch that requested a Copilot code review on every pull request targeting the default branch. As of August 7, 2026, GitHub has disabled the three settings that ruleset enabled: automatically requesting a Copilot review on every pull request, requesting an additional review on every new push, and requesting a review before a pull request is marked ready. The ruleset itself remains in affected repositories with these settings turned off, so teams can delete it if they choose, and any ruleset a team customized themselves is left untouched.
Why It Matters
The reversal follows direct developer feedback: as GitHub put it, "you told us that adding a reviewer should be your choice." Automatically opting every repository into Copilot reviews on every pull request removed control from teams that wanted to decide for themselves when and how AI review fits into their workflow. This change restores that choice as the default, without removing the underlying capability — Copilot code review itself is unchanged and can still be turned back on with a ruleset at the repository or organization level, and it continues to bill against a team's Copilot plan when used.
Availability
The change applies immediately to GitHub Code Quality on GitHub Enterprise Cloud and GitHub Team, and requires no action from repository owners who are happy with manual reviewer control.