Commit

Workflow

1. Analyze Changes: Run

   git status

   and

   git diff

   to identify the logic of changes.
2. Logical Grouping: Split changes for different features or modules into independent commits. Never submit unrelated changes in one single commit.
3. Generate Message: Create a standardized, English-only commit message for each group of changes.
4. Execute Automatically: Run

   git add .

   (or specific files) and

   git commit -m "<message>"

   in sequence.
5. Safe Push: Execute

   git push

   after completing all local commits.

Message Standards

• Language: Must use English.
• Format:

  <type>(<scope>): <subject>

  • Type: Must be selected from the following options:

    • feat

      : New feature

    • fix

      : Bug fix

    • docs

      : Documentation only changes

    • style

      : Changes that do not affect the meaning of the code (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

      : Changes to the build process or auxiliary tools and libraries
  • Scope: Optional, lowercase English, indicating the scope of changes (e.g., auth, parser, user-api).
  • Subject:
    • Use imperative mood, do not capitalize the first letter.
    • Do not add a period

      .

      at the end.
    • Be concise and clear, keep it within 50 characters.

Constraints

• No Emojis Allowed: Keep the message in plain text format.
• No Force Push Allowed: Ensure the safety of remote branches.
• Single-line Mode: The message must be a single line, no line breaks or body descriptions allowed.

Examples

• feat(auth): add google oauth2 support

• fix(db): resolve connection leak in production

• refactor(utils): simplify date format logic