summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYorick Peterse <yorickpeterse@gmail.com>2019-02-26 14:21:40 +0000
committerYorick Peterse <yorickpeterse@gmail.com>2019-02-26 14:21:40 +0000
commit08dc055135548792c8ae9e68f4032de7e0c6c3d3 (patch)
tree85b7d97d50a6111e136264e2d2180aa820596400
parent51eca040f6f60bb95307ac0e88081b47dc9d7012 (diff)
parent46acbb562ea5b1c6f16427ee23e81f7285d3522d (diff)
downloadgitlab-ce-08dc055135548792c8ae9e68f4032de7e0c6c3d3.tar.gz
Merge branch 'update-security-dev-workflow' into 'master'
Add task for adding links to the security release issue See merge request gitlab-org/gitlab-ce!25562
-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)