Strategies for enforcing commitizen

I’m not sure that this is the right place to open this but here goes; have there been any discussions on how to enforce commitizen? We started using it in a few projects at work but it’s both easy to forget and hard to make sure that everyone committing to the project respects it.

Maybe an idea would be to add a commitizen check master that checks all commits that have been added on this branch when compared to master. The exit code should be 0 (success) when all messages looks good.

This way we can run that as part of our CI step.

Any ideas?

[shogochiai]

My strategy is like this.

It prevents git commit locally, but don’t kill git-cz.

"scripts": {
    "warn-commit": "echo '\n\n\n\n Use `yarn commit` \n\n\n\n' && exit 1",
    "commit": "npx git-cz --no-verify"
}, 
"pre-commit": [
    "warn-commit"
]

[PrasoonDavid]

Use Husky to overide standard git commit

"hooks": {
    "pre-commit": "lint-staged",
    "commit-msg": "commitlint -E HUSKY_GIT_PARAMS",
    "prepare-commit-msg": "exec < /dev/tty && git cz --hook || true"
  }