From 2c6a3ab90402840cd39280f54315a18897577d0e Mon Sep 17 00:00:00 2001 From: Arnaud Roques Date: Sat, 30 Nov 2024 17:27:43 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9Ddocs:=20add=20a=20space=20after=20e?= =?UTF-8?q?moji?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CONVENTIONAL_COMMIT.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/CONVENTIONAL_COMMIT.md b/CONVENTIONAL_COMMIT.md index dd099c39e34..2dd77571e17 100644 --- a/CONVENTIONAL_COMMIT.md +++ b/CONVENTIONAL_COMMIT.md @@ -73,11 +73,12 @@ Each Gitmoji corresponds to a specific type of change: #### Guidelines for Using Gitmoji - Place the corresponding emoji at the beginning of the **description** in the commit message header. - Ensure the emoji aligns with the type and purpose of the change. +- Ensure a space is added immediately after the emoji. - Examples: - - `✨feat: add user authentication module` - - `🐛fix: resolve issue with null pointer exception` - - `🌱chore: add initial database seed script` - - `📝docs: update README with installation instructions` - - `🔥chore: remove deprecated API endpoints` + - `✨ feat: add user authentication module` + - `🐛 fix: resolve issue with null pointer exception` + - `🌱 chore: add initial database seed script` + - `📝 docs: update README with installation instructions` + - `🔥 chore: remove deprecated API endpoints` Using Gitmoji is optional but can make commit messages more engaging and informative.