Skip to content

Disable the security-target processor before the default merge is run

Steve Abrams requested to merge move-target-disable-step into master

What does this MR do and why?

We should disable the security-target processor before the default merge is run rather than after.

By disabling it before, we:

  • Guarantee nothing new will be linked and surprise us during the default merge and subsequent deployment
  • Guarantee nothing will inadevertently be unlinked, for example if a default merge pipeline fails for one issue, it doesn't get unlinked, and release managers see that it failed and can make a call on what to do next based on the severity of the issue (work to include it or unlink it).

This is a followup to this comment.

Author Check-list

  • [-] Has documentation been updated?
Edited by Steve Abrams

Merge request reports