-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Apply nixfmt #12349
Apply nixfmt #12349
Conversation
I do wonder if we should format the lang tests. After all, the parser should also work (and give correct position info) on inputs that aren't formatted correctly. Probably doesn't matter though... |
👍 I've excluded the Leaving them unformatted is annoying for contributors when enable format-on-save in their editor, so I think it's worth doing. |
... with nixfmt (rfc style)
8c89d57
to
c0e6692
Compare
I've reviewed the formatted
|
Carefully reviewed...
This does not include any automation for the release branch, but is based on that of #12349
This does not include any automation for the release branch, but is based on the configuration of #12349 pre-commit run -a nixfmt-rfc-style
is based on the configuration of #12349 pre-commit run -a nixfmt-rfc-style
This does not include any automation for the release branch, but is based on the configuration of #12349 pre-commit run -a nixfmt-rfc-style
This does not include any automation for the release branch, but is based on the configuration of #12349 pre-commit run -a nixfmt-rfc-style
Motivation
RFC 166
Now is a good time, because we're pretty much up to speed with backports.
I'll apply it to current maintenance branches as well, so that automated backports remain possible.
I will not add the automation to the maintenance branches though.
Context
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.