feat: add ability to restore cache by exact match #60
Conversation
This file contains hidden or 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
Signed-off-by: szymonmaszke <github@maszke.co>
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.
Overview
inputfor the actioncache-restore-exact-match(default:'false') - if 'true', will restore cache ONLY when theprimary-keymatches.jsfiles and regenerateddist.jsviapnpm run buildNow it should be possible to create workflows as outlined in #57 and #43:
Previously secondary restore-key would match even if the hashed dependency paths did not match.
Tests
cache-restore-exact-match: true, though I am not sure what the maintainers approach would beLet me know if you would like any additional changes (keep in mind I'm not JS dev though)
EDIT: FWIW tested
cache-restore-exact-match: truein one of my private repos and works as intended