Copilot code review: Independent repository rule for automatic reviews
You can now enable automatic Copilot code review with its own standalone repository rule. It’s generally available for Copilot users today ✨. Previously, triggering an automatic Copilot code review on pull request creation was only available as a subsetting of the Require a pull request before merging protection. Now you can adopt automatic reviews without adding merge gating policies, with subsettings for more control over your automatic review flow!
What’s new
The new rule includes subsettings to keep feedback up to date as your pull request evolves:
- Run on each push (reruns automatically when new commits are pushed to the pull request)
- Run on drafts (triggers for draft pull requests so authors can iterate before requesting human review)
With these changes, you can enable only what matches your or your team’s signal-to-noise preferences. For example, you might start with automatic reviews on creation only, then add on-push reviews for critical branches. Or you might include on-draft reviews in repositories when you want to iterate with Copilot code review before publishing your pull request.
Demo of Copilot code review highlighting an issue and providing a suggestion to apply in Xcode editor
Getting started
- Go to Settings > Rules > Rulesets in a repository you have admin access to.
- Add or edit a ruleset and select the new automatic Copilot code review rule.
- Choose the subsettings you want (on-push, on-draft).
- Save the rule and open a new pull request to see Copilot code review run automatically.
Learn more in the documentation.
Join the discussion within GitHub Community.