Modify setup-go cache key to work better with merge queues #416
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge queues work by creating a new branch on the repo to run CI on. Unfortunately, the caches are not shared between branches, so CI is always slower there than needed.
But, GHA can restore caches that come from
main
; this normally works, but the cache key I set up for oursetup-go
action was scoped per workflow, so we'd never grab it from say, the main CI build.Reconfigure this to try and restore caches a bit more.