Improve language when MR Security Report is outdated
Problem to solve
A recent issue #4913 (closed) was played to indicate to the user that the Security Report is outdated. The implementation offers advice to the user when the Report is deemed too old.
This issue aims to communicate a better approach to the user when the Report is outdated. There are two parts:
Security report is out of date. Retry the pipeline for the target branch
with something more appropriate
Replace the message Issues:
- I don't know how to retry a Pipeline. I don't think it's possible, unless it's considered that re-running every build is retrying the Pipeline.
- This message should only appear when the base commit SHA is the HEAD of the target branch. Given that is the case, it might be more appropriate to say something like
Security report is out of date. Run a new Pipeline for the target branch
.
✅ When a merge is closed or merged, the outdated message should not show
Issues: There is no action for the user to take, so we should not suggest one. Outdated messages should be hidden. !23575 (merged)
Intended users
Documentation
Update documentation regarding the MR widget to explain an outdated security report. https://docs.gitlab.com/ee/user/application_security/
What is the type of buyer?
Links / references
Edited by Seth Berger