-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add support for returning 0 on successful execution (with or without findings) #744
Comments
Decided to go in a slightly different direction with the |
v0.9.13 crashes for me:
Reverting back to v0.9.12 with |
Tested 0.9.13.4 and I'm happy with the solution 👍 |
"not sure about the flow here"? |
My apologies for not being clear. The “not sure about the flow” was related to whether I should close the ticket or someone else (I see the “close with comment” option) |
Reported based on using
pymarkdown
0.9.12.Today,
pymarkdown
returnsmode.strict-config
)Please consider changing so that scenario 2 above also returns 0, or that you add a configuration option to return 0 in that case (for example
--zero-on-success
or--success-code 0
).Background: I want to run pymarkdown from
subprocess.check_call()
which raises exceptions for all non-zero return codes.The text was updated successfully, but these errors were encountered: