Kissaki@programming.dev to Programming@programming.devEnglish · 2 days agoThe Pain That is GitHub Actions - Feldera Blogwww.feldera.comexternal-linkmessage-square22fedilinkarrow-up135arrow-down19cross-posted to: [email protected]
arrow-up126arrow-down1external-linkThe Pain That is GitHub Actions - Feldera Blogwww.feldera.comKissaki@programming.dev to Programming@programming.devEnglish · 2 days agomessage-square22fedilinkcross-posted to: [email protected]
minus-squarelemmeBelinkfedilinkarrow-up1arrow-down3·13 hours agoThey’re optional if you make them optional. I didn’t. You do as you please. 😄
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up3·12 hours 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-squarebamboo@lemm.eelinkfedilinkarrow-up1·3 hours 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