-
Notifications
You must be signed in to change notification settings - Fork 44.7k
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
Add flake8 linter workflow #923
Add flake8 linter workflow #923
Conversation
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.
I also suggest adding flake8 and the tests in a different PRs, and using the following small list of pep8 fixes:
python -m flake8 --select E303,W293,W291,W292,E305
This way we will start having pep8 but we won't break many PRs, and we gradually extend the list introducing minimal breakage.
The unit tests itself are added in a separate PR (here #865) already. I don't know if that's what you meant. As for the |
Well, I apologize then. Yes as for getting stricter you are right. |
No worries, I was just wondering 😅 |
Hi, your unit test PR has been merged, please can you resolve the conflicts in this one? Thanks |
6ef9f76
to
d780988
Compare
…t-Gravitas#923) * merging * clean commit * Delete mylearner.py This file is not needed. * fix py4j import error * more tolerant cancelling time * fix problems following suggestions * Update flaml/tune/spark/utils.py Co-authored-by: Li Jiang <bnujli@gmail.com> * remove redundant model * Update test/spark/custom_mylearner.py Co-authored-by: Chi Wang <wang.chi@microsoft.com> * add docstr * reverse change in gitignore * Update test/spark/custom_mylearner.py Co-authored-by: Chi Wang <wang.chi@microsoft.com> --------- Co-authored-by: Li Jiang <bnujli@gmail.com> Co-authored-by: Chi Wang <wang.chi@microsoft.com>
…8-workflow Add flake8 linter workflow
Background
I've recently opened a PR (#865) that will add automated unit tests using Github workflow for every PR and commit on the master branch. The suggestion was made to also add
flake8
linting, though in a separate PR, which you are looking at right now. I think it'd be a good idea to merge that other PR first and then append the workflow by merging this one.Changes
flake8
lintingflake8
linting job to the workflow (continue after error is set to true as there were still quite some linting issues)unit_tests.yml
toci.yml
as it now contains more jobs than just unit testsDocumentation
I've added a small section to
README.md
that explains how to run theflake8
linter.Test Plan
If the Python CI workflow succeeds the changes from this PR work as expected.
PR Quality Checklist
with multiple different prompts.(prompts N/A)and comprehensively.(needn't be comprehensive)