Build conventional commit messages following the Conventional Commits specification.
A new feature
Format
<type>(<scope>): <description> [optional body] [optional footer(s)]
Tips
Use imperative mood: 'add' not 'added'
Keep the header under 72 characters
Scope should be a noun describing the section of the codebase
Body explains the what and why, not the how
Breaking changes must be noted in footer with BREAKING CHANGE:
All types
β¨ featA new featureπ fixA bug fixπ docsDocumentation changesπ styleFormatting, missing semi-colonsβ»οΈ refactorCode refactoringβ
testAdding or updating testsπ§ choreBuild process or auxiliary tool changesβ‘ perfPerformance improvementsπ· ciCI/CD configurationπ¦ buildBuild system changesβͺ revertReverts a previous commit