Adds exit codes for detections/errors and machine-readable CSV output with an option #59
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
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.
Basically what the title says, I wrote some small changes to output an exit code of 2 if Fractureiser is detected (1 for actual caught errors), and added an argument that if set to "true", will output CSV logs (of the form
stage number,infected fileto stderr) for all detections (no logs will be output if nothing is detected).Basically this combines both solutions I mentioned into one and should fix #58, because I'm not sure which you'd prefer.
Edit: reworded the PR to link to the issue properly.