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?

Commencez par examiner la discussion sur l’issue #161 et le point d’entrée proposé `commitizen check master`. Définissez comment les commits ajoutés par rapport à master doivent être vérifiés et comment le succès ou l’échec doit être signalé pour CI ; l’issue ne nomme aucun fichier ni test pour commencer.

Rédigé par le modèle d'indexation à partir du texte de l'issue.