Copilot code review gets finer personal and enterprise controls

GitHub has expanded Copilot code review settings across its plans. Developers now get a dedicated page for automatic review preferences, including draft pull requests and new pushes, as well as a default effort level.

Enterprise administrators can set a review effort default that flows to organization-owned repositories, while organizations and repositories can override it. The changes are generally available, according to GitHub.

The controls that actually changed

The release separates several decisions that used to be easy to conflate. A developer can enable automatic reviews for their pull requests, decide whether draft pull requests and later pushes are included, and choose a default effort level. The enterprise can set a baseline, while organizations and repositories retain overrides.

GitHub's configuration guide describes Lite and Balanced effort levels and how personal settings and repository rules interact. Its review guide covers manual requests. The operational detail is that an automatic review from one setting does not necessarily cancel a review requested by another rule; teams should understand which policy is triggering the work.

A sensible rollout

Start where automated feedback is most useful: repositories with active review queues and clear ownership. Decide whether draft reviews help or merely produce noise before the code is ready. Measure useful findings and review time, not just the number of comments Copilot posted. Human reviewers still own architecture, behavior, and the final decision to merge.

Sources and further reading

• Original publication
• GitHub Docs: configuring Copilot code review
• GitHub Docs: requesting a Copilot review