Skip to content
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

fix: exit with "generic error" code instead of "vuls. found" code when no valid path is provided #86

Merged
merged 1 commit into from
Apr 24, 2022

Conversation

G-Rath
Copy link
Owner

@G-Rath G-Rath commented Apr 24, 2022

We exit with code 1 when there is at least one affected vulnerability, which isn't the case for this situation so we should instead exit with code 127.

@G-Rath G-Rath added the bug Something isn't working label Apr 24, 2022
@G-Rath G-Rath merged commit e261ae8 into main Apr 24, 2022
@G-Rath G-Rath deleted the fix-error-code branch April 24, 2022 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant