git-hooks.nix icon indicating copy to clipboard operation
git-hooks.nix copied to clipboard

Seamless integration of https://pre-commit.com git hooks with Nix.

Results 132 git-hooks.nix issues
Sort by recently updated
recently updated
newest added

When enabling `cargo-check.enable = true` I get this error: ``` cargo-check..............................................................Failed - hook id: cargo-check - exit code: 101 Updating crates.io index warning: spurious network error (2 tries remaining): [6]...

I tried setting `default_stages` to `[]`, but that didn't seem to work. :)

I'm having issues getting Prettier hook working. I see the entry in `.pre-commit-config.yaml` is ``` "/nix/store/6rq65zsjg4a07y0af936mqk7qjh7fdp7-node_prettier-2.2.1/bin/prettier --write --list-different --ignore-unknown" ``` For Prettier to actually _do_ anything I would expect to...

With nixos-unstable, I'm getting warnings like these ``` [WARNING] Unexpected key(s) present on local => nixpkgs-fmt: types_or [WARNING] Unexpected key(s) present on local => ormolu: types_or [WARNING] Unexpected key(s) present...

bug

pre-commit-hooks.nix in its current form is a package distribution by default; using pinned packages. Some users (me, #55?) prefer to provide their own packages only, in order to have consistent...

How can I integrate the supported hook from pre-commit such as `end-of-file-fixer` or `trailing-whitespace` into pre-commit-hooks.nix ?

`stylish-haskell` exits 1 on files it can't deal with, with a typical example being anything containing CPP. This is a "benign failure" in that it just means that it can't...

There's a guard to avoid doing the installation in a `lorri` shell by testing for the existence of git: https://github.com/cachix/pre-commit-hooks.nix/blob/e5ef518936a3f2f4575de064c74fb6383d2d330d/modules/pre-commit.nix#L304 This works fine... unless one happens to have also included...

Re: #72, it would be nice if `pre-commit-hooks` supported a "map"-like operation for tools or modes of tools that can only work a file at a time. One possible implementation...