We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When yarn is ran as part of a build for a Heroku application and the patches fail to apply, the exit code is 0. I expect it to be non-zero.
yarn
0
This means that a Heroku application will be deployed even if the patches failed to apply (!!).
This is happening because Heroku is not detected by the is-ci check.
is-ci
Related: #143
The text was updated successfully, but these errors were encountered:
Thanks for pointing this out!! This exit code business is such a minefield. Would adding a NODE_ENV=production check take care of it?
NODE_ENV=production
Sorry, something went wrong.
Would adding a NODE_ENV=production check take care of it?
In our case, yes, but some users might deploy to Heroku with NODE_ENV=staging 🤔
NODE_ENV=staging
No branches or pull requests
When
yarn
is ran as part of a build for a Heroku application and the patches fail to apply, the exit code is0
. I expect it to be non-zero.This means that a Heroku application will be deployed even if the patches failed to apply (!!).
This is happening because Heroku is not detected by the
is-ci
check.Related: #143
The text was updated successfully, but these errors were encountered: