gitmessage

gitmessage.txt

#
# A well-formed Git commit message is mandatory.
# Follow the Conventional Commits format with emojis:
# <type>(<scope>): <description> [emoji]
#
# Examples:
# feat(authentication): add Google auth provider ✨
# fix(api): fix a regression in user creation 🐛
# docs(readme): update contributing guide 📚
# refactor(db): rename user table to accounts 🔨
#
# ---
# Types:
# feat: A new feature
# fix: A bug fix
# docs: Documentation only changes
# style: Changes that do not affect code logic (white-space, formatting, etc.)
# refactor: A code change that neither fixes a bug nor adds a feature
# perf: A code change that improves performance
# test: Adding missing tests or correcting existing tests
# chore: Other changes that don't modify src or test files
# build: Changes that affect the build system or external dependencies
# ci: Changes to our CI configuration files and scripts
#
# Scopes: (optional, but encouraged)
# The part of the codebase affected by the commit. e.g., 'auth', 'frontend', 'api'.
#
# Emojis (optional, but encouraged):
# ✨ new feature
# 🐛 bug fix
# 📚 documentation
# 🎨 style
# 🔨 refactor
# 🚀 performance
# ✅ tests
# ♻️ refactoring of some sort (e.g., code cleanup)
# ⚙️ CI/CD or build system
# 📦 dependencies
# 🔖 release / version tags
# 🔒 security
#
# ---
# Body:
# A more detailed explanation of the commit.
#
# ---
# Footer:
# BREAKING CHANGE: A change that breaks backward compatibility.
# Closes #<issue number>
#
#
#
# Use this section below to write your commit message:
#
# ----------------------------------------------------
# <type>(<scope>): <description>
#
#
#
#
#
#
#