About automatic code review
By default, Copilot will only review a pull request when it is assigned to the pull request in the same way you would assign a human reviewer. However, repository owners can configure Copilot to automatically review all pull requests in the repository. Organization owners can configure Copilot to automatically review all pull requests in some or all of the repositories in the organization.
Triggering an automatic pull request review
After you configure automatic code review, Copilot will review pull requests in the following situations:
-
When a pull request is created as an "Open" pull request.
A review is not triggered if the pull request is created as a "Draft" pull request.
-
The first time a "Draft" pull request is switched to "Open".
Note
Copilot only automatically reviews a pull request once. If you make changes to the pull request after it has been automatically reviewed and you want Copilot to re-review the pull request, you must request this manually. To do this, click the button next to Copilot's name in the Reviewers menu.
Configuring automatic code review for a single repository
-
Sur GitHub, accédez à la page principale du référentiel.
-
Sous le nom de votre dépôt, cliquez sur Paramètres. Si vous ne voyez pas l’onglet « Paramètres », sélectionnez le menu déroulant , puis cliquez sur Paramètres.
-
Dans la barre latérale gauche, sous « Code et automatisation », cliquez sur Règles, puis sur Ensembles de règles.
-
Click New ruleset.
-
Click New branch ruleset.
-
Under "Ruleset name," type a name for the ruleset.
-
Under "Target branches," click Add target and choose one of the options—for example, Include default branch or Include all branches.
-
Under "Branch rules," select the Require a pull request before merging checkbox.
This expands a set of subsidiary options.
-
Select the Request pull request review from Copilot checkbox.
-
At the bottom of the page, click Create.
Configuring automatic code review for repositories in an organization
-
Dans le coin supérieur droit de GitHub, sélectionnez votre photo de profil, puis cliquez sur Vos organisations.
-
En regard de l’organisation, cliquez sur Paramètres.
-
Dans la barre latérale gauche, dans la section « Code, planification et automatisation », cliquez sur Référentiel , puis sur Ensembles de règles.
-
Click New ruleset.
-
Click New branch ruleset.
-
Under "Ruleset name," type a name for the ruleset.
-
Under "Target repositories," click Add target and choose either Include by pattern or Exclude by pattern.
-
In the dialog box that's displayed, type a pattern that will match the names of repositories in your organization—for example,
*feature
to match all repositories with names that end infeature
.For information about pattern-matching syntax, see Création des ensembles de règles pour les référentiels de votre organisation.
-
In the dialog box, click Add inclusion pattern or Add exclusion pattern.
-
Repeat the process for any additional patterns you want to add.
Note
You can add multiple targeting criteria to the same ruleset. Exclusion patterns are applied after inclusion patterns. For example, you could include any repositories matching the pattern
*cat*
, and specifically exclude a repository matching the patternnot-a-cat
. -
Under "Target branches," click Add target and choose one of the target options.
-
Under "Branch rules," select the Require a pull request before merging checkbox.
This expands a set of subsidiary options.
-
Select the Request pull request review from Copilot checkbox.
-
At the bottom of the page, click Create.