How to commit code? Use Conventional Commits!

[@marekmarkiewicz7723]

Nice episode. I have used similar approach ones when we where working with automatic tool for recognizing which part of semver number needs to be upgraded. Didn't know it is desribe as a convention :)

[@learnsoftwarearchitecture]

Thanks! How did your approach look like? What prefixes did you use?

[@marekmarkiewicz7723]

@@learnsoftwarearchitecture We have use fix and feat as commit prefix and 'BREAKING CHANGES' for bumping semver version (using semantic-release). I remember that we also use: docs, test and build. The bumping tool was using prefixes defined by Angular commit message format.

[@learnsoftwarearchitecture]

@@marekmarkiewicz7723 Cool! :) Btw. there is an npm package www.npmjs.com/package/commitlint and you can use e.g. Husky to define a hook that runs before a commit is created. It automates the process, so if you forget it or make a typo, it will fail while committing.