A commit message specification

Type (scope): Type (scope): Type (scope): Subject Note that the colon is followed by a space, and type is used to specify the type of commit. Only the following seven identifiers are allowed:

Type: Type indicates the type of commit

  • Feat: New Feature

  • Fix: Fixes bugs

  • -Jenny: There are some docs.

  • Style: format (changes that do not affect code execution)

  • Refactor: refactoring (i.e. code changes that are not new features or bug fixes)

  • Test: Adds a test

  • Chore: Changes to the build process or helper

If type is feat and fix, the commit will definitely appear in the Change log.

Scope: Optional, used to specify the scope of the commit

Subject: : commit A short description of the destination, no more than 50 characters, and no period at the end

Git branch specification

  • Master branch The master branch (protected branch) cannot modify code or commit directly on the master branch;
  • The Develop branch is the test branch, so the functionality that needs to be tested is merged into that branch.
  • The feature branch is the development branch. Everyone creates a separate feature branch based on different requirements and merges it into the Develop branch after development.
  • The fix branch is the bug repair branch, which needs to repair the released version according to the actual situation.