📄️ Good Commits
Commiting style is a very important component of working on any group based project and crucial when working in the industry.
📄️ Feat
The feat tag categorizes a change as one that brings in a new feature to the code/project and is one of the tags that will be used the most during initial development of a code base.
📄️ Fix
The fix tag categorizes a change as one that fixes a known issue with the code base and is one of the tags that will be used regularly during all stages of development.
📄️ Perf
The perf tag categorizes a change as one that aims to improve the performance of some aspect of the code/project and is one of the tags that will be used most after the initial development phase of the code base.
📄️ Refactor
The refactor tag categorizes a change as one that does not make any objective change in the code but improves internal structuring of the code without changing its external behavior.
📄️ Docs
The docs tag categorizes a change as one that makes changes to the documentation of the code either in the form of comments or related documentation files like the README.
📄️ Chore
The chore tag categorizes a change as one that handles miscellaneous management of the code base.
📄️ Build
The build tag categorizes a change as one that modifies the build process of the code base.
📄️ CI
The ci tag categorizes a change as on that alters the CI/CD pipeline of the project.
📄️ Style
The style tag categorizes a change as one that alters the styling of the code or any of its associated linters/formatters.
📄️ Test
The test tag categorizes a change as one that adds or alters any tests that are made for the code base.
📄️ Breaking Changes (!)
The breaking change tag ! is a special tag as it is the only tag that can be appended to any other commit tag described in this documentation.