skip to content

How do you get Copilot code review on every pull request in a repository, and does its review count toward required approvals?

level: middleimportance: should knowfreq 14%

answer

  1. a reviewer you request, or a rule
  2. a branch ruleset option
  3. personal settings and rulesets stay separate
  4. Comment, not Approve
  5. approvals are a public preview opt-in

basics

~20 s

Add a branch ruleset with Automatically request Copilot code review, optionally with Review new pushes. Copilot then leaves a Comment review, which does not count toward required approvals unless Copilot approvals (public preview, off by default) are enabled.

solid answer

~50 s

Manually, you request Copilot under **Reviewers** like a person, or request `copilot-pull-request-reviewer[bot]` through the REST API. For every pull request, create a branch ruleset (repository, organization or enterprise) with **Automatically request Copilot code review**, adding **Review new pushes** and **Review draft pull requests** if wanted; without Review new pushes it reviews once. Individuals can also turn on **Automatic Copilot code review** for their own pull requests. User settings and rulesets are separate and not hierarchical: either one triggers a review, Copilot posts only one, and a user cannot switch off push or draft reviews a ruleset enabled. By default Copilot leaves a **Comment** review, not Approve or Request changes, so it does not count toward required approvals. **Copilot approvals** are public preview and off by default; when enabled, an approving review satisfies the rule like a teammate's and is dismissed on new commits.

go deeper

for a junior

Recall that you request Copilot under Reviewers like a teammate, and that its default review is a Comment review that does not approve the pull request.

for a middle

Explain automatic review: the ruleset rule, Review new pushes and Review draft pull requests, and why user settings and rulesets never override each other.

for a senior

Show a rollout plan: a ruleset per repository set, a deliberate choice on new-push reviews against cost, and a clear statement that its comments advise rather than gate merges.

for a principal

Decide whether Copilot approvals should ever count toward merge requirements, where file-path limits make that tolerable, and who stays accountable for approving.

## Two ways to get a review **Copilot code review** is GitHub Copilot's automated reviewer for pull requests. It can be asked in two ways. - **Manually**: on the pull request, under **Reviewers**, click **Request** next to **Copilot**. Through the REST API, request `copilot-pull-request-reviewer[bot]` as a reviewer. A review usually takes under 30 seconds. - **Automatically**: through a **user's settings** or a **ruleset**, described below. By default Copilot reviews a pull request only when someone requests it. ## Automatic review configuration | Source | Where | Scope | |---|---|---| | User setting | Copilot settings, **Code review**, **Automatic Copilot code review** | Pull requests that user creates (Copilot Pro, Pro+, Max, or a Business or Enterprise licence; not managed user accounts) | | Repository ruleset | Settings, **Rulesets**, new branch ruleset, **Automatically request Copilot code review** | Pull requests in that repository | | Organization ruleset | Organization settings, repository **Rulesets** | Repositories matched by name patterns | | Enterprise ruleset | Enterprise-level branch ruleset | Targeted organizations and repositories | Each automatic source offers two options: 1. **Review new pushes**: review every new commit pushed to the pull request. Without it, Copilot reviews **once**, and you re-request with the button beside Copilot's name in **Reviewers**. 2. **Review draft pull requests**: review while the pull request is still a draft. Without it, the basic trigger is opening a pull request as open, or the first switch from draft to open. The key rule: a user's settings and a ruleset are **separate configurations, not a hierarchy**. Neither inherits from or overrides the other; a pull request is reviewed if **either** applies, Copilot posts **one** review even when both do, and you **cannot use your own settings to turn off** push or draft reviews that a ruleset turned on. ## What the review is By default Copilot leaves a **Comment** review, "not an 'Approve' review or a 'Request changes' review". Each comment carries a severity of High, Medium or Low, and many include suggested changes you can commit. Because it is a Comment review, it **does not count toward required approvals** and does not block a merge on its own. Replies you write to its comments are visible to people but not to Copilot, which does not answer them. A re-review may repeat comments you resolved or downvoted. Some files are excluded: dependency management files such as `package.json` and `Gemfile.lock`, log files and SVG files. Copilot reads repository instructions from the pull request's **head branch**, so changes to them can be tried in the same pull request. ## Copilot approvals (public preview) Every review's overview comment includes an **approval assessment**, which on its own counts for nothing. **Copilot approvals**, labelled public preview, change that: - Repository settings offer **Allow Copilot to approve pull requests** and **Allow Copilot approvals to count toward merge requirements**, plus optional **File paths** globs (up to 15) limiting which pull requests count. - Organizations choose Enabled everywhere, Let repositories decide, Enable for selected repositories or Disabled everywhere; at enterprise level the default is **Disabled everywhere**. - An approval is **dismissed** when new commits are pushed. ## Choosing a configuration 1. Decide the scope: a repository ruleset for one repository, an organization ruleset with name patterns for many, or an enterprise ruleset for the whole estate. 2. Decide on **Review new pushes**: it gives feedback on every iteration but costs a review per push; without it, people re-request reviews when they want them. 3. Decide on **Review draft pull requests**: useful for early feedback before humans are asked, at the cost of reviewing work in progress. 4. Tell the team what the review is: advisory comments with severities, not an approval, unless you deliberately enable Copilot approvals. 5. Leave personal settings to individuals; they add reviews but cannot subtract what a ruleset turns on. ## Effort and cost Reviews run at **Lite** or **Balanced** effort, with Balanced as GitHub's built-in default. Reviews consume AI credits and, on private repositories, GitHub Actions minutes for their agentic context gathering.

  • A developer turned off Automatic Copilot code review in their own settings, yet Copilot still reviews their pull requests and every push. Why?
    A ruleset applies. User settings and rulesets are separate, non-hierarchical configurations: a pull request is reviewed when either is enabled, and a user cannot use their own settings to turn off push or draft reviews that a ruleset enabled. Change or scope the ruleset if those reviews are unwanted.
  • You reply to a Copilot code review comment asking it to reconsider. What happens?
    Nothing from Copilot: replies are visible to people but not to Copilot, and it won't reply. To get a new verdict, re-request its review from Reviewers. To have the feedback implemented, use Fix with Copilot on the comment, which hands the work to Copilot cloud agent as a commit or a new pull request (passing suggestions to the cloud agent is in public preview).

  • Copilot code review approves the pull request when it finds nothing wrong.
  • My personal setting can switch off reviews that a repository ruleset requests.
  • Copilot re-reviews automatically on every push without any configuration.
  • Replying to a Copilot review comment makes it answer and revise its review.
  • Copilot approvals are generally available and on by default.