Draft: End-to-end spike for suggest vulnerability resolution
What does this MR do and why?
This MR is a POC to work out how the VR in MR flow will work. This builds on the other spike started in Draft: Diff to suggestion SPIKE (!163813 - closed) to create an MR suggestion from the LLM vulnerability resolution response.
This approach works by adding an optional argument to the GraphQL mutation for suggestionMergeRequestId
. With that value provided, the backend will create the resolution as a suggested change on the MR instead of creating a whole new MR.
Here's a quick video demo:
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.