Semantic Commit Guidance
This guide provides definitions and examples of semantic commits that you can use in your project. Each commit type should use a semantic label and description structure. This will facilitate collaboration among team members and improve the maintainability and comprehensibility of the project.
Commit Types and Descriptions
feat 🆕 – New Feature
fix 💥 – Bug Fix
chore ✴️ – Miscellaneous Changes
refactor ✏️ – Code Refactoring
docs 📄 – Documentation Updates
style 🎨 – Code Formatting and Style Changes
test ✅ – Test Updates
perf 🍀 – Performance Improvements
ci ➰ – Continuous Integration Related Changes
build ⚡ – Build System or External Dependency Changes
revert 🔙 – Revert a Previous Commit
add ✨ – Adding New File, Function, Method, Variable, etc.
remove 🔥 – Removing File, Function, Method, Variable, etc.
update 🆕 – Updating File, Function, Method, Variable, etc.
rename 🔁 – Renaming File, Function, Method, Variable, etc.
move 📦 – Moving File, Function, Method, Variable, etc.
copy ©️ – Copying File, Function, Method, Variable, etc.
security 🔒 – Security Related Changes
version 🔏 – Version Change
For an effective software team, commit messages should be descriptive and consistent. You can use the examples in this guide to document your project's changes with meaningful and well-labeled commits. By following this guide for your commits, you can improve the project's maintainability and enhance collaboration.
(Note: While using the example commits in real projects, it is essential to add more detailed commit descriptions suitable for your actual changes and use English and .md format for documentation.)