Article directory
The conventional commit specification is a lightweight convention based on commit information. It provides a simple set of rules to create a clear commit history; this is more conducive to writing automated tools. This convention mirrors SemVer by describing features, fixes, and breaking changes in commit messages.
| prefix | describe |
|---|---|
| feat | a new feature |
| fix | bug fix |
| perf | Code changes to improve performance |
| refactor | Code changes that neither fix bugs nor add new features |
| style | Changes that do not affect the meaning of the code (spaces, formatting, missing semicolons, etc.) |
| test | Add missing tests or fix existing tests |
| docs | Only documentation changes |
| ci | Change our ci configuration files and scripts |
| build | Changes affecting the build system or external dependencies (example scopes: gulp, broccoli, npm) |
| chore | Miscellaneous |
- Example:
git commit -m 'feat: 新增某某功能'