Skip to content

Allow security MRs targeting default branch to not have milestone

Reuben Pereira requested to merge rp/default-branch-no-milestone into master

What does this MR do?

We recently updated (gitlab-org/release/docs!389 (merged)) our security developer workflow to say that the MR targeting the default branch should not have a milestone.

This MR contains the following changes:

  1. Do not fail validation if a merge request targeting the default branch does not have a milestone set.

1. Fail validation if a merge request targeting the default branch has a milestone set. (Removed for now, since we see no benefit from validating this)

Author Check-list

  • Has documentation been updated?
Edited by Reuben Pereira

Merge request reports