ci: configure restore-keys for caches #1806
Merged
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.
restore-keys
is a configuration option for the actions/cache actionwhich specifies fallback behavior. The docs say it best:
So this improves caching when there's a miss. For example if I edit
.github/workflows/languages.toml
, the current behavior is that thecache for downloaded grammars will miss and all of them will need to
be fetched again. With
restore-keys
, we use the latest publishedcache as 'good enough', we'll fetch whatever grammars changed, and
then at the end we publish a new cache under the new hash.