Modify Action to Fail if Yarn Lock File Does Not Exist #129
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
threeal
force-pushed
the
action-fail-if-no-yarn-lock
branch
5 times, most recently
from
f037e5e to
4fdd5c8
Compare
threeal
force-pushed
the
action-fail-if-no-yarn-lock
branch
from
3324c78 to
7a534b3
Compare
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.
This pull request resolves #128 by introducing the following changes:
yarn.lockfile.getCacheKeyfunction to always return a cache key, even if theyarn.lockfile does not exist.test-action-without-lock-filejob from thetestworkflow.