Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upFeature: Set nonzero exit code with --critical #42
Comments
|
That's a good idea. We'd definitely want a way to distinguish between runtime errors (e.g., repository was corrupt) vs. size "errors"; for example, by returning different exit codes. |
|
I like this idea and I have some time to work on it. Following @mingalsuo description updating the tool to support custom user defined exit codes could be an approach. Have the user provide a config file with them listed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For automation purposes, it would be a great feature to be able to analyze repositories and get a machine readable exit code that states that critical issues were found.
One way is to directly have --critical set the exit code or add another flag that does that if critical issues were found.
Thanks for creating this great tool.