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 linter check for black and isort not failing when changes required #631

Merged
merged 1 commit into from
Nov 29, 2022

Conversation

lindsay-stevens
Copy link
Contributor

Noted here.

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.

Why is this the best possible solution? Were any other approaches considered?

It's the required arguments

What are the regression risks?

None, only relevant for GitHub actions

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No

Before submitting this PR, please make sure you have:

  • included test cases for core behavior and edge cases in tests
  • run nosetests and verified all tests pass
  • run black pyxform tests to format code
  • verified that any code or assets from external sources are properly credited in comments

- black and isort returncode is 0 when fixes required and applied, so
  add arguments that make it returncode 1 when fixes required
- flake8 and pycodestyle return 1 already
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.

2 participants