Security table incorrectly identifies a master merge
Problem Statement
We leverage a fancy table that helps us identify what issues are ready for a security release. Sometimes when changes occur, it will incorrectly state items are merged when that isn't actually the case: https://gitlab.com/gitlab-org/gitlab/-/issues/442641#note_1785561542
In the above example, an MR non-security, but linked to a security issue was targeting the default branch and merged. The usecase of a non-security MR on this is valid, but the bots reaction to indicate the merged MR is not. The security related MR was instead closed.
Milestones
-
Discuss how we want to appropriate handle this style of scenario -
Implement appropriate fixes to prevent misleading Release Managers