According to what I've seen used most in places where I've worked and also used in specific projects.
📕 Format
The following format for commits must be observed, the use of type is mandatory, it can be consulted in the topic below, the description depicts what action the current commit will perform:
<type>: <description>
🔷 Type
The types are as follows:
| Prefix | Definition | Sense |
|---|---|---|
| build | Builds | Changes that affect the build system or external dependencies (scope examples: npm, gulp) |
| chore | Tasks | Changes that do not modify test or source code files |
| ci | Continuous Integrations | Changes to our CI configuration files and scripts (example scopes: BrowserStack, Circle, Travis) |
| docs | Documentation | Documentation changes only |
| feat | Features | Some new functionality |
| fix | Bug Fixes | Bug fix |
| perf | Performance Improvements | Code change that improves performance |
| refactor | Code Refactoring | Code change that does not add functionality or fix a bug |
| revert | Revert | Reverts a previous commit |
| style | Styles | Changes regarding styling |
| test | Tests | Correction of existing tests or addition of missing tests |
Top comments (0)