Conversation
KyleGospo
force-pushed
the
cache
branch
2 times, most recently
from
b2e4584 to
42de939
Compare
Member
Author
|
@BoukeHaarsma23 Exploratory one, let me know your thoughts |
KyleGospo
force-pushed
the
cache
branch
2 times, most recently
from
cb412ef to
2608e4f
Compare
Restoration of the previous cache is intentionally skipped for tagged releases
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Saving of the cache is intentionally skipped for anything but tagged releases. All others will get a copy of the last tagged release's cache to accelerate things.