Skip to content

Latest commit

Β 

History

History
50 lines (40 loc) Β· 1.76 KB

File metadata and controls

50 lines (40 loc) Β· 1.76 KB

Clean Commit Workflow

When generating commit messages for this repository, follow the Clean Commit workflow.

Reference: https://github.com/wgtechlabs/clean-commit

Format

<emoji> <type>: <description>
<emoji> <type> (<scope>): <description>
<emoji> <type>!: <description>
<emoji> <type>! (<scope>): <description>

The 9 Types

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

Rules

  • Use lowercase for type
  • Use ! immediately after type (no space) to signal a breaking change β€” only for new, update, remove, security
  • Use present tense ("add" not "added")
  • No period at the end
  • Keep description under 72 characters

Examples

  • πŸ“¦ 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