diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-03-28 09:15:42 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-03-28 09:15:42 +0300 |
| commit | 66d107f9394f719c63cb30f53d62b5b5db888e4b (patch) | |
| tree | 0c0df62dcf91fdd2509e0428a1808f237d22ee18 /doc/development/code_review.md | |
| parent | 9449a8c94313cd1cbe1c4cad885635aa7e3f6c01 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/code_review.md')
| -rw-r--r-- | doc/development/code_review.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/development/code_review.md b/doc/development/code_review.md index ed9404187ae..5588afe0713 100644 --- a/doc/development/code_review.md +++ b/doc/development/code_review.md @@ -546,7 +546,9 @@ people who add commits to an MR are not authorized to approve or merge the MR an must seek a maintainer who has not contributed to the MR to approve and merge it. This policy is in place to satisfy the CHG-04 control of the GitLab -[Change Management Controls](https://about.gitlab.com/handbook/security/security-assurance/security-compliance/guidance/change-management.html). +[Change Management Controls](https://about.gitlab.com/handbook/security/change-management-policy.html). + +<!-- Or should it link to: https://about.gitlab.com/handbook/engineering/infrastructure/change-management/ ? --> To implement this policy in `gitlab-org/gitlab`, we have enabled the following settings to ensure MRs get an approval from a top-level CODEOWNERS maintainer: |