| > Good luck getting answers on those questions other than "read the source code" and then followed by "no, not that source code, this branch here". I experienced a similar situation last week with git-hooks.nix[1], a pre-commit integration for Nix. I wanted to run biome[2] checks on my repository during pre-push so I wrote a custom hook because git-hooks.nix has pre-defined integrations with prettier and rome, but not biome. Or that's what I thought. I eventually found out that the rome hook is actually referred as "rome" everywhere but calls biome instead[3]. This wasn't documented anywhere, so I opened an issue[4] suggesting to rename the hook to "biome" and keep the former for backwards compatibility reasons. As of today, this has been acknowledged by one of the maintainers, whose sole feedback has been to "thumb down" the issue. TL;DR: It's not just the documentation, but also the code not doing what you would expect. It also seems there's no means to improve the situation other than just forking the project since there's also clearly some kind of communication problem. [1] https://github.com/cachix/git-hooks.nix
[2] https://biomejs.dev/
[3] https://github.com/cachix/git-hooks.nix/blob/40e6053ecb65fcb...
[4] https://github.com/cachix/git-hooks.nix/issues/428 |
I've not seen such hilariously bad communication since trying to talk to my thesis advisor.
Guix might use a scheme, but at least it has good documentation and seems more open to accepting contributions.