@A_smart_kitten proposed the following:
(side note @jnuche, if the bot is flagging a closed security task as a train blocker, should it also reopen the task in question for additional visibility? i’m just thinking to avoid the potential risk of people seeing an already-closed train-blocker-subtask, and - based on its 'closed' status - thinking that the train-blocking issue has already been resolved.)
I'm in favor of that. Pinging @thcipriani and @sbassett for visibility
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| patches: ensure a security task notified of a failure is open | repos/releng/scap!790 | jnuche | T393361 | master |
IMO if SecurityPatchBot is resetting task priority, especially to UBN, it should definitely re-open the task if the task has been closed.
jnuche opened https://gitlab.wikimedia.org/repos/releng/scap/-/merge_requests/790
patches: ensure a security task notified of a failure is open
jnuche merged https://gitlab.wikimedia.org/repos/releng/scap/-/merge_requests/790
patches: ensure a security task notified of a failure is open