| applyTo | ** |
|---|
This repository follows the Clean Commit workflow for all commit messages.
Reference: https://github.com/wgtechlabs/clean-commit
<emoji> <type>: <description>
<emoji> <type> (<scope>): <description>
<emoji> <type>!: <description>
<emoji> <type>! (<scope>): <description>
| Emoji | Type | What it covers |
|---|---|---|
| π¦ | new |
Adding new features, files, or capabilities |
| π§ | update |
Changing existing code, refactoring, improvements |
| ποΈ | remove |
Removing code, files, features, or dependencies |
| π | security |
Security fixes, patches, vulnerability resolutions |
| βοΈ | setup |
Project configs, CI/CD, tooling, build systems |
| β | chore |
Maintenance tasks, dependency updates, housekeeping |
| π§ͺ | test |
Adding, updating, or fixing tests |
| π | docs |
Documentation changes and updates |
| π | release |
Version releases and release preparation |
- Use lowercase for type
- Use
!immediately after type (no space) to signal a breaking change β only fornew,update,remove,security - Use present tense ("add" not "added")
- No period at the end
- Keep description under 72 characters
π¦ new: user authentication systemπ§ update (api): improve error handlingποΈ remove (deps): unused lodash dependencyπ security: patch XSS vulnerabilityβοΈ setup: add eslint configurationβ chore: update npm dependenciesπ§ͺ test: add unit tests for auth serviceπ docs: update installation instructionsπ release: version 1.0.0π¦ new!: completely redesign authentication systemπ§ update! (api): change response format for all endpoints