You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .gitlab/issue_templates/Security developer workflow.md
+6-2
Original file line number
Diff line number
Diff line change
@@ -34,8 +34,12 @@ After your merge request has been approved according to our [approval guidelines
34
34
- You can use the script `bin/secpick` instead of the following steps, to help you cherry-picking. See the [secpick documentation]
35
35
-[ ] Create each MR targeting the stable branch `X-Y-stable`, using the [Security merge request template].
36
36
- Every merge request will have its own set of to-dos, so make sure to complete those.
37
-
-[ ] On the `Related merge requests` section, ensure that **ONLY**`4` merge requests are associated: **ONLY** one targeting `master` and the `3` backports.
38
-
-[ ] If there are more associated MRs, re-create another security issue and ensure there are only 4 merge requests associated with that one.
37
+
-[ ] On the `Related merge requests` section, ensure that **ONLY**`4` merge requests matching these conditions:
38
+
- From the security namespace (`gitlab-org/security`)
39
+
- Status is not `Closed`
40
+
- (Other MRs not matching these above conditions are acceptable)
41
+
-[ ] Among these `4` MRs, one targeting `master` and the `3` backports targeting stable branches.
42
+
-[ ] If there are more associated MRs, re-create another security issue and ensure there are only 4 merge requests associated with that one.
39
43
-[ ] If this issue requires less than `4` merge requests, add the ~"reduced backports" label.
0 commit comments