@[email protected] to [email protected]English • 1 month agoThe Pain That is GitHub Actions - Feldera Blogwww.feldera.comexternal-linkmessage-square28fedilinkarrow-up138arrow-down110cross-posted to: [email protected]
arrow-up128arrow-down1external-linkThe Pain That is GitHub Actions - Feldera Blogwww.feldera.com@[email protected] to [email protected]English • 1 month agomessage-square28fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilink-2•1 month agoThey’re optional if you make them optional. I didn’t. You do as you please. 😄
minus-square@[email protected]linkfedilink5•1 month agoNo, 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.
minus-square@[email protected]linkfedilink2•1 month agopre-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
They’re optional if you make them optional. I didn’t. You do as you please. 😄
No, they’re inherently optional in Git. There’s no way to “check in” a git hook. You have to put in your
READMEYou definitely need to actually check the lints in CI. It’s very easy though, just add
pre-commit run -ato your CI script.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