git提交commit格式标准:

The commit message should be structured as follows:

<type>(<scope>): <JIRA ticket number-subject>

The “<type>” field must be chosen from the options listed below:
build : Changes related to building the code (e.g. adding external libraries).

chore : Changes that do not affect the external user (e.g. updating the .gitignore file or .prettierrc file).

feat : Introduces a new feature to the codebase.

fix : A bug fix.

docs : Any changes that specifically relate to documentation (e.g. update comments for better code readability, update configuration file with new settings description, update installation instructions in README).

refactor : A code that neither fix bug nor adds a feature. (eg: This can used when there is semantic changes like renaming a variable/ function name).

perf : A code that improves performance style: A code that is related to styling.

test : Adding new test or making changes to existing test.


The “scope” field is optional and should be a noun that represents the part of the codebase affected by the commit, for example if the commit changes the submissions dashboard page, the scope could be “dashboard submissions“. If the commit affects multiple areas of the codebase, “global” or “all” could be used as the scope.

The “subject” field should be a brief description of the commit, written in the imperative present tense. It should not end with a period and the first letter should not be capitalized.

For example, “add new event builder step” or “fix bug in search functionality” are both appropriate subjects.

The introduction of the "subject" should always feature the Jira ticket number (SCIF-x).