Fix cache extraction error in Go vulnerability check workflow - #35
Conversation
The `golang/govulncheck-action` action manages its own Go setup and caching.
Having a separate `actions/setup-go` right before it caused cache extraction conflicts ("File exists" errors) because the vulnerability check action attempted to overwrite read-only cache files.
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
This PR removes the redundant
actions/setup-gostep from thego-vulnjob in.github/workflows/ci.yml.The
golang/govulncheck-actionaction automatically manages its own Go setup and caching. Setting up Go with caching immediately before it caused cache extraction conflicts, as the vulnerability check action attempted to overwrite read-only cache files created by the first setup step, resulting intar"File exists" errors.PR created automatically by Jules for task 10405030060081909192 started by @arran4