Explore adding commitizen as a precommit hook

[six7]

Let's integrate commitizen as a precommit hook in the plugin codebase: https://commitizen-tools.github.io/commitizen/

[macintoshhelper]

Pros

• Consistent commit messages across different developers
• Can help with semantic versioning and possibly be a better alternative to changesets
• Makes sure there is extra context on historical changes

Cons

• conventional-changelog might conflict with changesets
• Requires Python/Homebrew and requires contributors to have it installed as a global system package – extra onboarding steps
• Breaks muscle memory of git commit -m

Suggested Actions

• Discussion around whether to
  • Have commitizen as an optional/recommended commit step
  • Require commitizen with Husky
  • Use a commit message convention/format
• Recommend including issue numbers in commits
• Recommend prefixing commits with fix/feat/test/ci, etc to use as a tag for the context of the commit – e.g. Angular Commit Message Format https://github.com/angular/angular/blob/main/CONTRIBUTING.md#-commit-message-format

Amount of Time to Implement: Small (mainly discussion, Husky is already used)

Resources

• https://www.freecodecamp.org/news/how-to-write-better-git-commit-messages/