-
Notifications
You must be signed in to change notification settings - Fork 5
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: add script for linting & formatting code #116
ci: add script for linting & formatting code #116
Conversation
FYI: we have some formatting checks in place here. Here you propose CI to make formatting commits if it doesn't fulfil the requirements. In addition, the I do like the approval for executing the CI! |
Thanks for doing this Tin!
|
Nothing against auto-formatting. Nightly allows for a few additional nice things it seems (e.g. grouping imports) if desired, and as shared elsewhere, appears to be in use by the Polkadot SDK: https://github.com/paritytech/polkadot-sdk/blob/master/docs/contributor/STYLE_GUIDE.md. Agree with Peter, probably best to manually address clippy warnings for now. |
Instead of adding an additional workflow, can we rather rename |
Also imagine that this might create some 'churn' for those that dont auto-format locally, whereby branch is pushed, CI formats and adds a commit and then local branch is out of sync. This can hopefully be eliminated by a proper local setup, which probably enforces formatting locally more so than currently. Either you sort it out to avoid any hassle, or GH sorts it for you and you have to cope with any hassle. |
For this reason, is it then not more simple if we do a CI check on nightly and have the developer fix it themselves? |
Hence, I think would be better to have:
|
…k-format-script' into pr/116
…k-format-script' into pr/116
…k-format-script' into pr/116
This reverts commit 4cc6655.
As there are a huge conflict in this PR, I will close it and create the another. |
Link to issue: #115