Resolve "Improve language when MR Security Report is outdated"
What does this MR do?
This is implementation for #198015 (closed) which aims to improve the language and UX for the outdated Security Report.
The backend changes here are to set new pipeline path for the project, so frontend can use it to provide a direct link to the user.
Screenshots
a) User is ahead of target branch
When the MR shows that the Security Report is out of date, the user simply needs to run a new Pipeline on the target branch.
| Before | After |
|---|---|
 |
 |
b) User is behind target branch
When the MR shows that the Security Report is out of date, the user must rebase/merge to get the most recent target branch changes. This will take them to situation a), where the Security Report will either be in date or they can run a new target branch pipeline.
| Before | After |
|---|---|
 |
 |
Does this MR meet the acceptance criteria?
Conformity
Edited by Dheeraj Joshi