-
Notifications
You must be signed in to change notification settings - Fork 14
Workflow autofixes #195
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
base: master
Are you sure you want to change the base?
Workflow autofixes #195
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
Can we leave the "
vs '
alone?
I have generally followed convention of using '
for "programmer" values and "
for "user-facing" values (e.g. messages)
There are also some bits of formatting I'm not particularly impressed with where it breaks some lines across multiple lines in a way which makes them more difficult to read (particularly list comprehensions)
Also worth mentioning that this does cause a lot of noise in git blame
which generally provides more value than some of the less valuable lint changes
f8ce19d
to
4792c48
Compare
Looks a lot better with this config 👍 thanks |
5dbfdb6
to
913a94a
Compare
@ca-johnson this is now just the python
I'm comfortable with that set now becoming incremental-linting fixes, though before doing that I'd extend the readme to explain the workflow. WDYT? |
6663658
to
7254592
Compare
Changes
The automatic fixes applied via
pre-commit run --all-files
, stacked on #194.I don't think I'd land this in one go, particularly; this is more illustrative. I also probably would choose to not land this until after CI runs pre-commit for incremental linting.
Verification