π Commit Guidelines | SafeTrust
This guideline establishes clear conventions for commit messages and branch naming in this project. Following these conventions ensures a consistent and readable commit history.
π οΈ General Rules
- ALL BRANCHES AND COMMIT MESSAGES SHOULD BE IN LOWERCASE.
- Keep commit messages short and descriptive (less than 72 characters).
π³ Branch Naming Convention
Use the following branch prefixes based on the type of change:
feat/ π: For new features
fix/ π: For bug fixes
remove/ ποΈ: For file removals
docs/ π: For documentation updates
style/ π¨: For style changes (formatting, spacing, etc.)
refactor/ β»οΈ: For code refactoring (no functional changes)
perf/ β‘: For performance improvements
test/ π§ͺ: For adding or fixing tests
build/ ποΈ: For build system changes
ci/ π: For CI/CD configuration changes
change/ βοΈ: For small changes or tweaks
chore/ π οΈ: For maintenance tasks
Example Branch Names
feat/user-registration π
fix/product-price-validation π
docs/readme-update π
style/button-styling π¨
βοΈ Commit Message Convention
Commit Message Format
Each commit message should follow this structure:
<type>: <short description>
Commit Types
feat π: A new feature
fix π: A bug fix
docs π: Documentation changes
style π¨: Changes that do not affect code behavior (e.g., formatting)
refactor β»οΈ: Code changes without affecting functionality
perf β‘: Performance improvements
test π§ͺ: Adding or fixing tests
build ποΈ: Changes to the build system or external dependencies
ci π: Changes to CI/CD scripts
chore π οΈ: Maintenance tasks or other minor changes
Writing Commit Messages
- Keep It Short: Less than 72 characters for the title.
- Be Clear: Explain what was done and why (if necessary).
- Use Present Tense: Write commit messages as if you're giving commands.
Example Commit Messages
feat: add user registration support π
fix: resolve price validation bug π
docs: update API usage instructions π
style: adjust button alignment π¨
perf: optimize database queries β‘
π Thank You for Following the Guidelines
By adhering to these guidelines, you help maintain a clean and professional repository. Let's build great things together! π
π Commit Guidelines | SafeTrust
This guideline establishes clear conventions for commit messages and branch naming in this project. Following these conventions ensures a consistent and readable commit history.
π οΈ General Rules
π³ Branch Naming Convention
Use the following branch prefixes based on the type of change:
feat/π: For new featuresfix/π: For bug fixesremove/ποΈ: For file removalsdocs/π: For documentation updatesstyle/π¨: For style changes (formatting, spacing, etc.)refactor/β»οΈ: For code refactoring (no functional changes)perf/β‘: For performance improvementstest/π§ͺ: For adding or fixing testsbuild/ποΈ: For build system changesci/π: For CI/CD configuration changeschange/βοΈ: For small changes or tweakschore/π οΈ: For maintenance tasksExample Branch Names
feat/user-registrationπfix/product-price-validationπdocs/readme-updateπstyle/button-stylingπ¨βοΈ Commit Message Convention
Commit Message Format
Each commit message should follow this structure:
Commit Types
featπ: A new featurefixπ: A bug fixdocsπ: Documentation changesstyleπ¨: Changes that do not affect code behavior (e.g., formatting)refactorβ»οΈ: Code changes without affecting functionalityperfβ‘: Performance improvementstestπ§ͺ: Adding or fixing testsbuildποΈ: Changes to the build system or external dependenciesciπ: Changes to CI/CD scriptschoreπ οΈ: Maintenance tasks or other minor changesWriting Commit Messages
Example Commit Messages
feat: add user registration supportπfix: resolve price validation bugπdocs: update API usage instructionsπstyle: adjust button alignmentπ¨perf: optimize database queriesβ‘π Thank You for Following the Guidelines
By adhering to these guidelines, you help maintain a clean and professional repository. Let's build great things together! π