Add workflow to manually update the lib cache #4376
Merged
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
ponylang-main
added
the
discuss during sync
We cache `lib` in order to speed up our builds as building all of LLVM takes a long long time. Once an update to any of the files that would invalidate the cached libs is done, until a new cached version is done on "main", it won't apply to new PRs. This workflow allows us to update (if needed) the lib cache for any given branch. In general, this would usually only be used on `main`.
SeanTAllen
force-pushed
the
manual-llvm-cache
branch
from
07e3d0f
to
6b7d3e3
Compare
ponylang-main
removed
the
discuss during sync
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.
We cache
libin order to speed up our builds as building all of LLVM takes a long long time. Once an update to any of the files that would invalidate the cached libs is done, until a new cached version is done on "main", it won't apply to new PRs.This workflow allows us to update (if needed) the lib cache for any given branch. In general, this would usually only be used on
main.