Submit form
<type>(<scope>): <subject>
// 空一行
<body>
Description
1. type (required)
Used to describe the category of commit
- br: This item is specifically for the bug number, and is used to report the bug modification status of the bug list to the test
- feat: new features (feature)
- fix: fix
- docs: documentation
- style: Format (does not affect changes in code operation)
- refactor: refactoring (that is, it is not a new feature, nor a code change to modify a bug)
- test: add test
- chore: Other small changes. Generally, only one or two lines of changes, or small changes submitted several times in a row belong to this category
- revert: feat(pencil): add'graphiteWidth' option (withdraw the previous commit)
- upgrade: upgrade
- bugfix: fix bugs
- optimize: optimize
- perf: short for Performance, improve code performance
- test: add test cases or update existing tests
- ci: The main purpose is to modify the project to continue to complete the integration process (such as Travis, Jenkins, GitLab CI, Circle) submission
- build: The main purpose is to modify the submission of the project build system (such as glup, webpack, rollup configuration, etc.)
2. scope (optional)
Scope is used to describe the scope of the commit's influence, such as the data layer, control layer, view layer, etc., depending on the project.
3. subject (required)
Subject is a short description of the purpose of the commit, no more than 50 characters.
Start with a verb, use the first-person present tense, such as change, instead of changed or changes
. The first letter is lowercase and
ends without a period (.)
4. body (optional)
Part is a detailed description of this commit, which can be divided into multiple lines