GitHub Code Quality がレビュアーとして Copilot を自動追加しなくなりましたGitHub Code Quality no longer adds Copilot as a reviewer

GitHub has changed the default behavior of its Code Quality feature so that enabling it on a repository no longer creates a ruleset that automatically requests a code review from GitHub Copilot on pull requests. The adjustment matters because it removes an implicit dependency between a repository's quality tooling and Copilot's automated review, giving teams clearer control over when and how AI-assisted reviews are triggered.

Previously, turning on GitHub Code Quality would provision a ruleset as part of the setup. That ruleset added Copilot as an automatic reviewer, meaning any new pull request opened against the covered branches would trigger a request for Copilot to weigh in alongside human reviewers. For teams that wanted this behavior, it was a convenient shortcut. For others, it could produce unexpected review requests, add noise to pull request threads, or bundle an AI review policy with a feature that was primarily intended to surface code quality signals. By decoupling the two, GitHub appears to be aligning the feature with a more explicit, opt-in model for automated reviewers.

According to the changelog, the key practical detail is the split between new and existing repositories. Going forward, enabling Code Quality will not generate the reviewer ruleset at all. In repositories that already have the ruleset in place from a prior activation, the configuration is not removed automatically. Those teams will need to manage reviewer settings manually if they want to change the current behavior, which likely means editing or deleting the existing ruleset through the repository or organization rules interface. Administrators who relied on the automatic Copilot review should therefore verify their current state rather than assume the change propagates retroactively.

To understand the impact, it helps to know how the underlying pieces fit together. Rulesets are GitHub's mechanism for defining and enforcing policies on branches and tags, functioning as a more flexible successor to classic branch protection rules. A ruleset can require status checks, restrict who can push, enforce linear history, and require pull request reviews, among other controls. Requiring a review from a specific reviewer, including Copilot, is one of the behaviors a ruleset can encode. Because rulesets are configuration objects that persist independently, a policy created during one setup step does not disappear simply because the default that created it has changed.

GitHub Code Quality is part of GitHub's broader push to give development teams automated signals about the health of their codebases, sitting alongside related capabilities such as code scanning, secret scanning, and Dependabot within the platform's code security and quality tooling. Copilot code review, meanwhile, is the AI-assisted review capability that can analyze a pull request's diff and leave suggestions or comments the way a human reviewer might. Both features can be valuable, but they serve distinct purposes, and combining them by default blurred the line between measuring quality and mandating an AI reviewer. The decoupling makes each feature's scope more predictable.

The change also reflects a wider industry pattern in which AI review and assistant features are increasingly offered as deliberate opt-ins rather than defaults baked into unrelated settings. As automated reviewers from GitHub and competing platforms become more common, teams have raised questions about review volume, cost, signal quality, and governance over how AI participates in the development workflow. Making the Copilot reviewer an explicit choice, rather than a side effect of enabling Code Quality, is consistent with that direction and reduces the chance of surprising behavior for organizations that did not intend to enroll every pull request in AI review.

For teams evaluating what to do next, the practical steps are straightforward. Repositories newly enabling Code Quality should not expect Copilot to be added as a reviewer and can configure that separately if desired. Repositories that already have the auto-request ruleset should decide whether to keep, modify, or remove it, since the update does not touch existing configurations. Anyone who wants Copilot to continue reviewing pull requests can still add it as a reviewer through the appropriate ruleset or review settings. As with any changelog update, checking GitHub's official documentation for the current setup flow is advisable, since details and interfaces can evolve over time.