-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GIT GUIDELINE π #35
Comments
This was referenced Dec 12, 2024
6 tasks
This was referenced Jan 22, 2025
This was referenced Jan 26, 2025
This was referenced Jan 28, 2025
This was referenced Feb 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
π 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! π
The text was updated successfully, but these errors were encountered: