Does GitHub Copilot coding agent review its own PRs first?

Does GitHub Copilot coding agent review its own pull requests before I see them

No. GitHub Copilot can open or review a pull request, but you still review the branch and the comments yourself before merging. GitHub’s docs describe Copilot’s review as feedback, not a substitute for your review process, and they tell you to check the pull request thoroughly before merging.

The part people get wrong is the word “review.” Copilot can be asked to review its own output, and GitHub can also run automatic pull request reviews before a PR is switched from draft to open. That still does not mean the agent has passed the work for you. The docs say Copilot leaves comments, suggests fixes, and you should read through the review output before merging.

If Copilot is configured for automatic review, it may inspect the pull request before you even open it, including while the PR is still a draft. GitHub says automatic review can trigger when you create an open pull request, when you switch a draft PR to open, on new pushes, or on draft pull requests, depending on the repository settings. That is earlier review, not self-approval.

Copilot’s review is not a required approval. GitHub says Copilot always leaves a Comment review, not an Approve or Request changes review, and those reviews do not count toward required approvals or block merging. If your repository requires human approvals, another reviewer still has to sign off.

The inconvenient part is that Copilot can miss things your workflow depends on. GitHub tells you to review the output and iterate, and it recommends checking the pull request thoroughly before merging. In other words, Copilot can reduce the amount of manual work, but it does not replace the person who owns the change.

The simplest mental model is this: Copilot can look at its own PR, leave notes, and even do it before the PR is public in the normal sense, but you still see the changes, read the comments, and decide whether the branch is ready. If you want a second place to keep the process visible, DevConnect keeps the same principle for app testing: the owner controls the work, and the feedback loop stays explicit.

If you want to confirm what happened on a specific PR, open the PR page and check the review activity in the sidebar or the review comments themselves. GitHub also documents a manual request flow, where you ask Copilot for a review by adding it as a reviewer, then read the resulting comments like any other review.

A practical workflow is to let Copilot draft or review the branch, then scan the diff for logic errors, test coverage gaps, and anything the agent may have interpreted from the wrong file or instruction set. GitHub notes that Copilot reads repository instructions and agent skills from the head branch, which means the review can be shaped by what is already on that branch. That is useful, but it also means the branch contents matter before you trust the result.

If Copilot leaves comments that are not right, you can request a re-review or push more commits. GitHub documents both paths, and it says Copilot reviews are meant to be iterated on, not treated as a final sign-off. The right question is not whether Copilot reviewed its own PR first, but whether you reviewed the PR after Copilot did.