diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-31 09:06:29 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-31 09:06:29 +0000 |
| commit | 6026bddcd51eca573c530240c421392045172b89 (patch) | |
| tree | 30cb1134ac00a336e6cfaa81bbafe6cd1360f58f /doc/development/code_review.md | |
| parent | b7c776f95d5f41ac00986073563ad0c1de4bad44 (diff) | |
| download | gitlab-ce-6026bddcd51eca573c530240c421392045172b89.tar.gz | |
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, 2 insertions, 2 deletions
diff --git a/doc/development/code_review.md b/doc/development/code_review.md index a19f40d1824..77c57bb332d 100644 --- a/doc/development/code_review.md +++ b/doc/development/code_review.md @@ -170,8 +170,8 @@ Maintainers should check before merging if the merge request is approved by the required approvers. Maintainers must check before merging if the merge request is introducing new -vulnerabilities, by inspecting the list in the Merge Request [Security -Widget](../user/project/merge_requests/index.md#security-reports-ultimate). +vulnerabilities, by inspecting the list in the Merge Request +[Security Widget](../user/application_security/index.md). When in doubt, a [Security Engineer](https://about.gitlab.com/company/team/) can be involved. The list of detected vulnerabilities must be either empty or containing: |