diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-04 18:17:50 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-04 18:17:50 +0000 |
| commit | 17a58755f31fcca5f6f42a4f7de1bbf1934dd038 (patch) | |
| tree | 42b09381de05e0a8b046242f109d451ddf5cfff5 /.gitlab/issue_templates | |
| parent | 1b723130416e59bdaef5d662a33f22ac1d3ce953 (diff) | |
| download | gitlab-ce-17a58755f31fcca5f6f42a4f7de1bbf1934dd038.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to '.gitlab/issue_templates')
| -rw-r--r-- | .gitlab/issue_templates/Security developer workflow.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/.gitlab/issue_templates/Security developer workflow.md b/.gitlab/issue_templates/Security developer workflow.md index 3a210c358e5..5c1b669a88f 100644 --- a/.gitlab/issue_templates/Security developer workflow.md +++ b/.gitlab/issue_templates/Security developer workflow.md @@ -15,6 +15,7 @@ MUST be linked for the release bot to know that the associated merge requests sh - Fill out the [Links section](#links): - [ ] Next to **Issue on GitLab**, add a link to the `gitlab-org/gitlab` issue that describes the security vulnerability. - [ ] Add one of the `~severity::x` labels to the issue and all associated merge requests. +- [ ] If this change affects the public interface (public API or UI) of the product, post in the `#support_gitlab-com` Slack channel to explain the impact and discuss a mitigation plan for users that might be affected. If you need Support feedback or approval, reach out in `#spt_managers` Slack channel or mention `@gitlab-com/support/managers`. ## Development |