build: Use setup-go action cache. #3168
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
davecgh
force-pushed
the
build_use_setup_go_cache
branch
from
796321d
to
bb98a79
Compare
dajohi
approved these changes
Aug 2, 2023
The latest version of the setup-go action now caches the go module and build cache by default, so it should no longer be done separately to avoid saving the same data under two different cache keys. This updates the caching logic accordingly to remove those directories from the separate cache step and renames the step to reflect that it now only involves the lint cache. Finally, while here, it also switches the key over to use the hash of the 'go.sum' file in the root of the repository as opposed to using the commit hash as it produces significantly less cache objects.
davecgh
force-pushed
the
build_use_setup_go_cache
branch
from
bb98a79
to
9be168d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The latest version of the setup-go action now caches the go module and build cache by default, so it should no longer be done separately to avoid saving the same data under two different cache keys.
This updates the caching logic accordingly to remove those directories from the separate cache step and renames the step to reflect that it now only involves the lint cache.
Finally, while here, it also switches the key over to use the hash of the 'go.sum' file in the root of the repository as opposed to using the commit hash as it produces significantly less cache objects.