Today, the automation of fixes tends to generate PRs that then need to be evaluated before accepting the PR. This feature would turn that process around, by allowing me to instruct co-pilot to use Docker Scout's knowledge of vulnerabilities to help me "scaffold out" fixes based on the recommendations, in the context of my codebase, ideally within my IDE, in a way that more naturally fits my development flow.
Today, the automation of fixes tends to generate PRs that then need to be evaluated before accepting the PR. This feature would turn that process around, by allowing me to instruct co-pilot to use Docker Scout's knowledge of vulnerabilities to help me "scaffold out" fixes based on the recommendations, in the context of my codebase, ideally within my IDE, in a way that more naturally fits my development flow.