1.9 KiB
1.9 KiB
Related issues
Developer checklist
- Make sure this merge request mentions the GitLab Security issue it belongs to (i.e.
Related to <issue_id>
). - Merge request targets
master
, orX-Y-stable
for backports. - Milestone is set for the version this merge request applies to. A closed milestone can be assigned via quick actions.
- Title of this merge request is the same as for all backports.
- A CHANGELOG entry is added without a
merge_request
value, withtype
set tosecurity
- Assign to a reviewer and maintainer, per our Code Review process.
- For the MR targeting
master
:- Ping appsec team member who created the issue and ask for a non-blocking review with
Please review this MR
. - Ensure it's approved according to our Approval Guidelines.
- Ping appsec team member who created the issue and ask for a non-blocking review with
- Merge request must not close the corresponding security issue, unless it targets
master
.
Note: Reviewer/maintainer should not be a Release Manager
Maintainer checklist
- Correct milestone is applied and the title is matching across all backports
- Assigned to
@gitlab-release-tools-bot
with passing CI pipelines
/label ~security