Fix linter check for black and isort not failing when changes required #27
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
…quired - Linters black and isort returncode is 0 when fixes required and applied, so add arguments that make it returncode 1 when fixes required. Linters flake8 and pycodestyle` return 1 already.
lindsay-stevens
force-pushed
the
linter-fix
branch
from
88052b6 to
9fcaa98
Compare
lognaturel
approved these changes
Jan 24, 2023
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.
Linters
blackandisortreturncode is 0 when fixes required and applied, so add arguments that make it returncode 1 when fixes required. Lintersflake8 andpycodestyle` return 1 already.What has been done to verify that this works as intended?
Same as XLSForm/pyxform#631
Why is this the best possible solution? Were any other approaches considered?
It's the required arguments
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
None, only relevant for GitHub actions
Do we need any specific form for testing your changes? If so, please attach one.
No
Does this change require updates to documentation? If so, please file an issue here and include the link below.
None
Before submitting this PR, please make sure you have:
testsnosetestsand verified all tests passpython bin/pre_commit.pyto format / lint code