Skip to content

GIT GUIDELINE 🐈 #3

Description

@JosueBrenes

πŸš€ 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

  1. Keep It Short: Less than 72 characters for the title.
  2. Be Clear: Explain what was done and why (if necessary).
  3. 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! πŸš€

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions