I disagree with the usage of githooks for linting and testing. It discourages frequenting committing which is a tenet of using git. Commit often, perfect later,

I disagree with the usage of githooks for linting and testing. It discourages frequenting committing which is a tenet of using git. Commit often, perfect later, publish once (https://sethrobertson.github.io/GitBestPractices/ https://sethrobertson.github.io/GitBestPractices/). Your pipeline should be responsible for ensuring things don't make it into the master branch that shouldn't. Run tests and linting on a pull request and make it a requirement for those to pass in order to merge the PR. Otherwise one of two things is going to happen: 1. People will not commit frequently and you will have a commit history that isn't as granular as it should be. 2. People will just bypass the githook check TBH I think some of this stems from people's fear of rebasing. I've heard so many times, "But it rewrite's the history". Yes, but it's the history on YOUR branch. Nobody should care what you to do your branch and it is yours to perfect. You should want to rewrite the history of your branch in my opinion. If you're committing frequently there will inevitably be some commits you want to squash or fixup.