Automataically re-run target branch's pipeline if security results are outdated
Problem to solve
We tell users when security results in an MR are outdated (#4913 (closed)), but they are required to take a manual step to re-run the target pipeline. This manual step means users could potentially get frustrated or do not get as much value out of latest security results as possible.
Intended users
Further details
-
Determine what expected behavior is in these cases. -
Identify edge cases around automatng this
Proposal
- Detect when the target branch's pipeline is out of date and re-run the pipeline
- This should be the default behavior
- Provide a way to disable this behavior
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by Nicole Schwartz