-
Notifications
You must be signed in to change notification settings - Fork 470
New issue
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
[Bug] Exit code always 0 #194
Comments
Yes, we should definitely return a proper exit code. |
Curious about how to go about making this change. These are the guts of the Lines 148 to 182 in 855f565
If this is updated to ensure all branches return a Promise that resolves or rejects as expected, would it be as simple as adding a jscodeshift/bin/jscodeshift.sh Lines 110 to 114 in 855f565
|
+1 |
I have a PR up to fix this, but haven't had much luck getting reviews. Anyone know the best way to approach getting this change merged? |
jscodeshift executions always exits with code
0
, regardless of whether there were any errors. Here is my output, although this is generic to any situation where you have a non-zeroerrors
count.Would the best practice instead be to set an exit code that's non-zero if there are any
errors
? In the current implementation, it's not intuitive to create anexec
wrapper or the like in order to execute jscodeshift programmatically.The text was updated successfully, but these errors were encountered: