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
pre-commit: apply black formatting (and prettier on one yaml file) #755
Conversation
cc61607
to
b0f345f
Compare
b0f345f
to
1120466
Compare
@manics @yuvipanda @choldgraf what do you think? The PR list is down from 20 to 1 single stale PR with very little changes, can we go for a full Waiting for this to get merged is somewhat of a blocker to start doing more work as well. |
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'm +1 on merging this - the remaining PR isn't complicated enough that it would be majorly disrupted by this. I think it'd be OK to merge so that we don't start to create conflicts when new PRs come up
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!
Thanks @manics @choldgraf! I'll go for a merge |
I've applied black formatting now. I ran it once first without string normalization, applied some manual tweaks, and then ran it with string normalization.
String normalization isn't systematically used with black in the jupyterhub org. I personally favor it though and figure it could make sense to do while also applying black in the first place - something that is reasonable to do only when the amount of PRs are low.