-
-
Notifications
You must be signed in to change notification settings - Fork 389
pre-commit hook is broken in nix #2967
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
Comments
To be fair this has been merged for 5 months. No one has raised any objections or issues since. It would seem like nix users are in the minority. The original intention was to make it so users didn't have to copy the json from documentation. Is there a third option that can satisfy both parties? |
I'm assuming the |
I noticed the last change to |
I haven't really been using the flake-based shell so I'm not sure. Perhaps we could try using something like https://github.com/cachix/pre-commit-hooks.nix ? I think that generates |
|
Why did we commit |
I had made an unrelated change to the config, and someone had suggested to commit it directly rather than have users copy the config directly. |
More context: |
Considering not everyone is using Nix to develop HLS, ignoring So I'm planning to:
|
this breaks |
@teto Oh, nice catch! I only tested |
Currently,
nix develop
complains:This problem was introduced by #2679, where
.pre-commit-config.yaml
was checked in git.But according to our documentation,
.pre-commit-config.yaml
should be managed by Nix. People do not use Nix can just manually installpre-commit
hook and paste the file content into.pre-commit-config.yaml
haskell-language-server/docs/contributing/contributing.md
Lines 171 to 216 in 09968a1
Now we have two options to compare:
pre-commit
config from Nix, and update the docs accordingly..pre-commit-config.yaml
from Git, and let Nix manage it again..pre-commit-config.yaml
I recommend the second option, as Non-Nix users will have some manual setups anyway, and we were on option 2 before #2679 was merged.
The text was updated successfully, but these errors were encountered: