diff options
author | Marin Jankovski <maxlazio@gmail.com> | 2019-01-28 12:21:42 +0100 |
---|---|---|
committer | Marin Jankovski <maxlazio@gmail.com> | 2019-01-28 12:51:37 +0100 |
commit | e4db1a615b9f30574c063bda9f6183654f74586e (patch) | |
tree | fa720c79e5f429f7900461f9974a93b0d98bde29 /.gitlab/issue_templates/Security developer workflow.md | |
parent | 436a43346729745b3aeba214b27de937c65f062e (diff) | |
download | gitlab-ce-e4db1a615b9f30574c063bda9f6183654f74586e.tar.gz |
Create security release MR template
Improve existing issue templates for security releases
Diffstat (limited to '.gitlab/issue_templates/Security developer workflow.md')
-rw-r--r-- | .gitlab/issue_templates/Security developer workflow.md | 13 |
1 files changed, 5 insertions, 8 deletions
diff --git a/.gitlab/issue_templates/Security developer workflow.md b/.gitlab/issue_templates/Security developer workflow.md index f9bf700f809..4bc4215d21b 100644 --- a/.gitlab/issue_templates/Security developer workflow.md +++ b/.gitlab/issue_templates/Security developer workflow.md @@ -3,20 +3,17 @@ Create this issue under https://dev.gitlab.org/gitlab/gitlabhq -Set the title to: `[Security] Description of the original issue` +Set the title to: `Description of the original issue` --> -### Prior to the security release +### Prior to starting the security release work - [ ] Read the [security process for developers] if you are not familiar with it. - [ ] Link to the original issue adding it to the [links section](#links) - [ ] Run `scripts/security-harness` in the CE, EE, and/or Omnibus to prevent pushing to any remote besides `dev.gitlab.org` -- [ ] Create an MR targetting `org` `master`, prefixing your branch with `security-` -- [ ] Label your MR with the ~security label, prefix the title with `WIP: [master]` -- [ ] Add a link to the MR to the [links section](#links) -- [ ] Add a link to an EE MR if required -- [ ] Make sure the MR remains in-progress and gets approved after the review cycle, **but never merged**. -- [ ] Add a link to this issue on the original security issue. +- [ ] Create a new branch prefixing it with `security-` +- [ ] Create a MR targeting `dev.gitlab.org` `master` +- [ ] Add a link to this issue in the original security issue on `gitlab.com`. #### Backports |