Cache builds in GitHub actions #899
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.


This reduces time to deploy our previews by only building what is needed. These builds tend to take 1-2 minutes but I have also noticed frequent network related intermittent failures with e.g. Math docs that this will avoid on unrelated PRs.
Downside is we need to keep the cache key computation for frontend updated when changing any in-repo dependencies but I think it's worth it.