-
-
Notifications
You must be signed in to change notification settings - Fork 526
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
GitHub Pull Request Template Update #927
Conversation
# Conflicts: # .github/PULL_REQUEST_TEMPLATE.md
pyflakes here is given only certain subdirectories because `.` will try and run across all packages installed in the virtual environment, if the virtual environment is within the project's root folder (which is my common practice).
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.
lgtm
Thank you!
@minchinweb Thanks for this. Out of curiosity, do you have |
No, I don't have invoke might be a good pure-Python alternative that I've used in the past that might do what you want. |
That's great; I was actually hoping you didn't have it. Would you mind going through the contributing doc and getting set up? I'd love your notes on whether there's enough info there or not for the Windows setup. |
Forgot to @minchinweb for the above comment. |
* Improve GitHub PR Template * suggest running commands with `poetry run ...` pyflakes here is given only certain subdirectories because `.` will try and run across all packages installed in the virtual environment, if the virtual environment is within the project's root folder (which is my common practice).
Further to #911, this aims to improve the Pull Request template, by including a reminder of the commands to run locally for test, lints, etc.
Checklist