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

Don't call parse on empty outputs #375

Merged
merged 1 commit into from
Sep 21, 2023
Merged

Don't call parse on empty outputs #375

merged 1 commit into from
Sep 21, 2023

Conversation

mfussenegger
Copy link
Owner

@mfussenegger mfussenegger commented Sep 21, 2023

More general approach to #365
Instead of fixing each linter one by one, just don't call them if there
is no output.

More general approach to #365
Instead of fixing each linter one by one, just don't call them if there
is not output.
@mfussenegger mfussenegger merged commit 67f74e6 into master Sep 21, 2023
3 checks passed
@mfussenegger mfussenegger deleted the empty-output branch September 21, 2023 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant