Add save-if
option for conditional cache saving
#21
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.
Objective
Closes #20.
Sometimes you don't always want to save the new cache, but only restore from existing caches.
This might be necessary if the repository is very active and always hits the cache size limit.
For example, you might only want to save the cache on the main branch and reuse it across all branches.
See also bevyengine/bevy#13040.
Solution
Add a
save-if
option, allowing you to specify when the cache should be saved.Defaults to
true
.Unfortunately, the
cache
action does not provide asave-if
option, so we need to conditionally usecache/restore
instead.Internally, we add a new job step to determine the cache paths, key and fallbacks such that we can reuse them consistently.This turned out to be more difficult to get working than to just copy and paste everything, we will just have to be careful to keep the values in sync.