Appearance
π§© Emoji Commit Convention β
This document defines the official Emoji Commit Convention used by the Socle-Commun ecosystem.
π Table of Contents β
π― Goal β
Unify commit messages in all repositories using a clear, visual, and minimal format β especially suitable for small teams and open-source projects.
π Format β
plaintext
<emoji> (#issue-id) commit message
Element | Required | Description |
---|---|---|
emoji | β | Type of change (see list below) |
(#issue-id) | πΆ | Reference to GitHub/GitLab issue (optional) |
commit message | β | Short and direct description (in English) |
π« No text prefixes like
feat:
,fix:
, etc. β the emoji replaces it.
β Examples β
plaintext
β¨ (#12) add new endpoint for fragment creation
π (#45) fix path encoding issue on Windows
π update contributing guidelines
π¨ clean up CSS formatting
π Allowed Emojis β
Emoji | Name | Meaning |
---|---|---|
β¨ | :sparkles: | New feature |
π | :bug: | Bug fix |
β»οΈ | :recycle: | Refactor / code cleanup |
π₯ | :fire: | Remove code / files |
β | :white_check_mark: | Tests |
π¨ | :rotating_light: | Fix lint / build / warnings |
π | :memo: | Documentation update |
π | :lipstick: | UI styles / cosmetic changes |
π¨ | :art: | Code formatting |
π | :rocket: | Deploy or performance improvement |
π§ | :wrench: | Config or tooling |
π | :repeat: | Workflow / automation |
π¦ | :package: | Dependency / release related |
β | :heavy_plus_sign: | Add dependency / file |
β | :heavy_minus_sign: | Remove dependency / file |
π§© You can extend this list β but keep it small and consistent.
π§ Good Practices β
- β Always start your commit with one emoji
- π§Ύ Use simple, clear English messages
- π’ Reference issues with
(#id)
if possible - π« Never use
feat:
,fix:
, etc. - π Squash before merging to keep a clean history
β Why Emoji Commits? β
- π Easier to scan commit history
- π₯ Better async communication
- β¨ Emphasizes change type visually
- π Works well in mono-repos and open source