List of issues with pre-commit #15
Replies: 4 comments
-
I work on sail-riscv. We added a markdown link checker lint recently. For some reason it fails... even when I haven't edited any markdown files:
When I accidentally pushed the exact same commit to my work's internal Gitlab it worked fine! Apparently then there are no files to check...
Same commit though. Apparently it matches markdown files and I definitely haven't edited any of those. No idea what is going on here. I think the actual error is because it requires a newer version of Node than the one Rocky 9 comes with (16), but yeay what a nice error message, and why is it running that check anyway? |
Beta Was this translation helpful? Give feedback.
-
From a collegue:
Someone linked to an earlier thread and...
|
Beta Was this translation helpful? Give feedback.
-
From a collegue:
"Just upgrade pre-commit" you might think. Well, it's not so easy, as the following conversation shows:
Using |
Beta Was this translation helpful? Give feedback.
-
We often ran into this error with hadolint and eventually gave up and disabled it:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This is my collection of issues me and my colleagues have had with
pre-commit
's reliability (and the reliability of the linters). I'm collecting these so when people say "but it works for me; you must be doing something wrong" I can point them here.Beta Was this translation helpful? Give feedback.
All reactions