summaryrefslogtreecommitdiff
path: root/.gitlab
diff options
context:
space:
mode:
authorHeinrich Lee Yu <heinrich@gitlab.com>2019-02-26 21:26:19 +0800
committerHeinrich Lee Yu <heinrich@gitlab.com>2019-02-26 21:26:19 +0800
commit46acbb562ea5b1c6f16427ee23e81f7285d3522d (patch)
tree923dd463110dd019d683d2e125e9ee396c5ec6de /.gitlab
parentfb76dfe0d8e9f99731f37c2da5d7cc2522365ceb (diff)
downloadgitlab-ce-46acbb562ea5b1c6f16427ee23e81f7285d3522d.tar.gz
Add task for adding links to the sec release issue
Diffstat (limited to '.gitlab')
-rw-r--r--.gitlab/issue_templates/Security developer workflow.md1
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 aaa16145399..9946651075f 100644
--- a/.gitlab/issue_templates/Security developer workflow.md
+++ b/.gitlab/issue_templates/Security developer workflow.md
@@ -30,6 +30,7 @@ Set the title to: `Description of the original issue`
#### Documentation and final details
- [ ] Check the topic on #security to see when the next release is going to happen and add a link to the [links section](#links)
+- [ ] Add links to this issue and your MRs in the description of the security release issue
- [ ] Find out the versions affected (the Git history of the files affected may help you with this) and add them to the [details section](#details)
- [ ] Fill in any upgrade notes that users may need to take into account in the [details section](#details)
- [ ] Add Yes/No and further details if needed to the migration and settings columns in the [details section](#details)