## Current setup Currently, we're using `angular` preset. It'll display following commit types: - feat: A new feature. - fix: A bug fix. - perf: A code change that improves performance. - revert: Reverts a previous commit. Other commit types like `chore`, `docs`, `style`, `refactor`, `test`, `build`, and `ci` are generally not included by default because they are considered internal changes or changes that do not directly affect the application behavior or functionality from the user's perspective. we can include new commit types if needed, please tell me if you feel so. ## Commit msg format Each commit message consists of a **header**, a **body** (optional), and a **footer** (optional). The header has a special format that includes a **type**, an **optional scope**, and a **subject**. For example: ``` <type>(<scope>): <subject> <body> <footer> ``` ### Header Header is mandatory and must conform to the following format: ``` <type>(<scope>): <subject> ``` - type: The type of change being committed (see below for details). - scope: A noun describing the section of the code affected by the commit (optional). - subject: A brief summary of the change (max 50 characters, no period at the end). ### Subject The subject contains a succinct description of the change: - Use the imperative, present tense: "change" not "changed" nor "changes". - No capital letter at the beginning. - No period (.) at the end. ### Body The body includes a longer description of the change and why it is being made: - Use the imperative, present tense: "change" not "changed" nor "changes". - Include the motivation for the change and contrast this with previous behavior. ### Footer The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit Closes. Breaking Changes should start with the word `BREAKING CHANGE`: with a space or two newlines. The rest of the commit message is then used for this. Example: ``` fix: handle keys exception Closes #123. ```