doc/user/project/merge_requests/reviews/automatic_reviewer_assignment.md
{{< details >}}
{{< /details >}}
{{< history >}}
auto_assign_code_owner_reviewers. Disabled by default.auto_assign_code_owner_reviewers removed.{{< /history >}}
When you enable automatic reviewer assignment, GitLab assigns the
Code Owners of changed files as reviewers on a merge request.
You don't have to select reviewers from the CODEOWNERS file by hand.
CODEOWNERS file.To turn on automatic reviewer assignment for a project:
After you turn on the setting, GitLab assigns Code Owners as reviewers when:
GitLab assigns every Code Owner that matches the files changed in the merge request.
GitLab skips auto-assignment when:
@GitLabDuo is excluded from this check.{{< history >}}
dap_powered_recommend_reviewers. Disabled by default.{{< /history >}}
[!flag] The availability of the Assign reviewers with GitLab Duo Agent Platform strategy is controlled by a feature flag. For more information, see the history. This feature is available for testing, but not ready for production use.
When GitLab Duo Agent Platform is available for your project, the Automatic reviewer assignment section shows a Reviewer assignment strategy setting in place of the single checkbox. Select one of these options:
CODEOWNERS
file that matches the changed files.When you select this strategy, GitLab Duo Agent Platform reads the required approval rules on the merge request. For each rule, it recommends the minimum number of reviewers needed to satisfy the rule, assigns them, and adds a note that explains the choice. This strategy applies to all approval rule types, not only Code Owners.
To choose between the eligible approvers for a rule, GitLab Duo Agent Platform considers the following for each approver:
GitLab assigns reviewers when the merge request becomes ready, the same as the code owners strategy. The recommendation runs in the background, so the reviewers might take a moment to appear. GitLab ignores approval rules that require zero approvals.