chore(ci): deduplicate yarn cache by removing the set-up-job action
#8504
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
This avoids caching yarn dependencies under two different keys.
jtoar
changed the title
set-up-job actionset-up-job action
|
4 replays were recorded for 640afc0.
|
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.
Follow up to #8449. With that PR in now, we have two yarn caches going at the same time that have the same content but different keys because most jobs still use the
set-up-jobaction instead of the newset-up-yarn-cacheaction.This does not affect how the test project is cached, it only deduplicates the caching for the framework's dependencies.