-
Notifications
You must be signed in to change notification settings - Fork 19
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
Apply flake8 suggested fixes and add flake8 GitHub CI action with black compatible config #29
Comments
Fixed some more things, only one error left. |
Thanks for the introduction of flake8 CI and the fixes found with it. I hadn't had a chance yet to compare flake8 formatting results against those of black, apologies for the delay in feedback. @dirkmueller addressed this in d522754. Going forward, we'll need to maintain the flake8 configuration for zero-diff to black output when discrepancies are encountered. |
@jfkw flake8 is just complaining, it isn't reformatting anything. |
Black remains the preferred formatter and allows long lines. Add flake8 config extend-ignore E501 line too long to supress those warnings.
Default configuration of flake8 recommended wrapping long lines previously accepted by the black formatter. Revert some of these line changes to reduce overall diff for security reviewers and to assist automatic rebase of open PRs currently in review.
Black remains the preferred formatter and allows long lines. Add flake8 config extend-ignore E501 line too long to supress those warnings.
Default configuration of flake8 recommended wrapping long lines previously accepted by the black formatter. Revert some of these line changes to reduce overall diff for security reviewers and to assist automatic rebase of open PRs currently in review.
Fix incorrect manual revert of flake8 line shortening with the black formatter. The CI job for the black formatter is configured. Upon PR or push, black CI job will exit with failure if there is diff to what has been committed.
We can close this issue now. Thanks everyone for their patience with the noisy commits as we configured and experimented with the configuration of the new CI jobs. |
As I prepared a PR today and wanted to make sure I do not introduce errors, I linted the go_modules file using flake8.
I fixed two easy things and added a flake8 GitHub Action:
#28
Not sure if this is desired?
The text was updated successfully, but these errors were encountered: