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
[MRG] Add lint-action workflow #1711
Conversation
mrbean-bremen
commented
Oct 9, 2022
•
edited
edited
- evaluate as replacement for Pep8Speaks, relate to Further CI improvements #1121
- testing only...
Codecov Report
@@ Coverage Diff @@
## master #1711 +/- ##
==========================================
+ Coverage 97.58% 97.60% +0.01%
==========================================
Files 66 66
Lines 10744 10744
==========================================
+ Hits 10485 10487 +2
+ Misses 259 257 -2
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
@darcymason - I found the action reviewdog/action-flake8, which does annotations. Please have a look at the diff, if this is what you had in mind. We could use this instead of Pep8Speaks. We already do flake8 checks, have to check if we can use the settings from that check, and replace that also. |
Yeah, this looks pretty good. I think we might as well use action-black as well, might as well try to standardize the formatting as code comes in. |
f64ebc0
to
8c09a7d
Compare
@darcymason: Not sure about black - I enabled it and configured it to check all files (instead of the diff only), and it shows a few things in example code, but doesn't really say what exactly is wrong (you may check the curent diff). Also, there seem to be some general limits for this kind of annotations, so not all warnings are shown:
I will change it to only check the diff, maybe it is still helpful... for the time being I would leave it at warnings only (e.g. no failed build on findings). flake8 is now configured as before: first for errors, which will fail the build (as you had seen in a previous run), and afterwards for style warnings, which will not fail the build. Bothe are run on the diff, but I can see that there are a lot of warnings (but no errors) outside the diffs:
I may leave it as is for the time being, and we can later check what to change... what do you think? |
Agreed.
I agree with this also.
I think "as is" still includes |
No, I left that only in so you can see the diff. Will change this now... |
- use same flake8 arguments as before
8c09a7d
to
08fc246
Compare
I actually don't remember where Pep8Speaks is configured, in case we want to remove it... |
Found it, under Settings / Applications. I would suggest to leave it in for a time even if we merge this, to see if it finds stuff that flake8 does not. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Lets merge it in and se how things go...