Skip to content

🧩 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
ElementRequiredDescription
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 ​

EmojiNameMeaning
✨: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

PubliΓ© sous licence MIT