-
Notifications
You must be signed in to change notification settings - Fork 144
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
Annoy black #293
Annoy black #293
Conversation
Okay nice. The flake8 lints work with annotations. |
@Reckless-Satoshi
looks fine for now. What do you think? The reason you don't see black annotating the commits is that they get fixed due to |
1d7cc5d
to
7c5e2e4
Compare
7c5e2e4
to
384591b
Compare
I think it's a way better set up than what we had before! 😄 Thank you very much for getting this done 🚀 |
Final test I guess -- merging this should run the auto-fix and commit it to main branch. |
Merged. Auto-fix did not add a new commit, possibly because it also needs |
@Reckless-Satoshi Yes, I was also having second thoughts about it :D. A bot commit changes to main is definitely an uncomfortable feeling. I guess we don't autofix then -- commit annotations are more than enough. The auto-fixing part can be documented/enforced using pre-commit, but again, it just formatting, so don't think it's that serious - on the fence with this..you decide xD |
@Reckless-Satoshi Oh the reason It didn't auto-fix is because of this - https://github.com/redphix/robosats/blob/1dea4e73b6410ca741c85a4b6c4b8ab2e2649bcb/.github/workflows/py-linter.yml#L36 |
What does this PR do?
annoy black
Checklist before merging
cd frontend; npm run format
. If it's a mobile app feature I rancd mobile; npm run format
.