Skip to main content

Reviewing a pull request created by Copilot

After Copilot creates a pull request you should review it and comment on anything that needs changes.

Who can use this feature?

Copilot coding agent is available with the GitHub Copilot Pro+ and GitHub Copilot Enterprise plans in repositories where it is enabled.
Sign up for Copilot

Note

Copilot coding agent is in public preview and subject to change.

Reviewing Copilot's changes

After Copilot has finished working on a coding task, and has requested a pull request review from you, you should review Copilot's work thoroughly before merging the pull request.

Important

If you have the "Required reviews" rule or branch protection enabled, you won't be able to approve pull requests that you initiated by assigning the related issue to Copilot. Someone else must approve the pull request before it can be merged.

You can ask Copilot to make changes using pull request comments, or you can check out Copilot's branch and make changes yourself.

Tip

We recommend you batch your review comments instead of submitting them individually.

When you leave a comment on Copilot's pull request, Copilot will consider your comment, and decide whether to start a new agent session to respond.

If Copilot starts a new agent session in response to your comment, Copilot will react with 👀, and a "Copilot has started work" event will appear in the pull request timeline.

Screenshot of a pull request timeline with a review comment with the eyes reaction and a "Copilot started work" timeline event.

Copilot may ignore a comment if it considers that the comment was not intended for it. If you are sure that you want Copilot to respond to your comment, you can @mention Copilot by including @copilot in your comment.

Tip

If you don't want Copilot to respond to comments on a pull request, you can unassign Copilot from the pull request. If you later reassign Copilot to the same pull request it will respond to new comments and push more changes. It will not respond to comment that were added while it was not assigned.

For more information, see the section "Use comments to iterate on a pull request" in Best practices for using Copilot to work on tasks.

Managing GitHub Actions workflow runs

GitHub Actions workflows will not run automatically when Copilot pushes changes to a pull request.

GitHub Actions workflows can be privileged and have access to sensitive secrets, so you should review code written by Copilot before allowing workflows to run.

To allow GitHub Actions workflows to run, click the Approve and run workflows button in the pull request's merge box.

Screenshot of the merge box on a pull request from Copilot with the "Approve and run workflows" button.

Giving feedback on Copilot's work

You can provide feedback on Copilot's work using the feedback buttons on Copilot's pull requests and comments. We use your feedback to improve the product and the quality of Copilot's solutions.

  1. On a pull request or comment from Copilot, click the thumbs up (👍) or thumbs down (👎) button.
  2. If you click the thumbs down button, you're asked to provide additional information. You can, optionally, pick the reason for your negative feedback and leave a comment before clicking Submit feedback.

Further reading

OSZAR »