ci: Add cache key to build job #217
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
|
@jamesread is attempting to deploy a commit to the Listinai Team on Vercel. A member of the Team first needs to authorize it. |
|
@jamesread the build is failing, can you sync your fork with main? Edit: nevermind! :) I enabled the setting that allowed me to. |
naruki1024
pushed a commit
to naruki1024/postiz-app
that referenced
this pull request
Jan 10, 2025
…add-cache ci: Add cache key to build job
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.
@jonathan-irvin Current builds on this job are not actually using the cache, I think this may be due to having a cache key not set (like I did with the eslint job), so it makes sense to add it here to at least be the same as the other job.