The Pain That is Github Actions
www.feldera.com
Developing a complex CI pipeline with github actions is full of gotchas.
  • FizzyOrange@programming.dev
    41·
    1 day ago

    To check that people ran the pre-commit linters.

    Committing itself won’t be possible

    That’s not how pre-commit hooks work. They’re entirely optional and opt-in. You need CI to also run them to ensure people don’t forget.

      • FizzyOrange@programming.dev
        3·
        1 day ago

        No, they’re inherently optional in Git. There’s no way to “check in” a git hook. You have to put in your README

        Clone the repo and then please run pre-commit install! Oh and whatever you do don’t git commit --no-verify!

        You definitely need to actually check the lints in CI. It’s very easy though, just add pre-commit run -a to your CI script.

        • bamboo@lemm.ee
          2·
          16 hours ago

          pre-commit also has a free service for open source GitHub repos too. They’ll even push an autofix commit for you if your tools are configured for it