-
Notifications
You must be signed in to change notification settings - Fork 322
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
CI: drop code formatters #558
Conversation
Codecov Report
@@ Coverage Diff @@
## master #558 +/- ##
==========================================
+ Coverage 77.58% 78.03% +0.44%
==========================================
Files 115 115
Lines 6701 6701
==========================================
+ Hits 5199 5229 +30
+ Misses 1502 1472 -30
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Will we have a different formatter like |
good question, personally I am not happy about it, pls ask @ananyahjha93 or @tchaton |
we’ll add any formatters that can work automatically for users. but right now this is a blocker for new contributors. imagine coming to do a simple contribution of a few lines, and you spent the next 2 hours trying to get the build to pass because you have no idea what black, mypy, isort etc are. you walk away and don’t come back because it’s too “hard” to contribute. so, we lose contributors and gain a few sorted lines... not worth it |
I see. That totally makes sense. |
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 ! Should we add note in PR header to explain how to do formatting if people are interested ?
What does this PR do?
requested by @williamFalcon
Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃