A minimalist approach toward
git commit
to keep commits simple.
Minimal commit is a Node.js based CLI (command line interface) tool that helps you and your team mates to stay consistent with the git commit
messages. To commit files using Minimal Commit, you have a list of options to choose from, this list consist type of work you did. This makes things simple and less confusing by choosing an option from a list.
The list of options is limited to only nine types. This is done on purpose to keep the list as short as possible to avoid confusion. The more options you have, the more confusing it will be.
Following are the nine types of commits.
β¨ feat
to be used for a new featureπ fix
to be used for bug fixesπ₯ break
to be used for breaking changesβ»οΈ ref
to be used for making code/folder refactorπ§ͺ test
to be used for writing test casesπ ver
to be used for version changesπ docs
to be used for documentationπ¨ style
to be used for CSS changesπ config
for configuration, and dependencies changesπ¦ misc
to be used for others
To install Minimal Commit, you can use the following command.
npm install -g minimalcommit
- Straight Forward
- Easy to read
- Visually appealing
mct
Hereβs the general syntax of Minimal Commit.
<type>: <message>
β οΈ All of the commits must be written in the present tense. Following are some examples:
β¨ feat: added sign-up feature β
β¨ feat: add sign up feature β
π config: removed extra extension files β
π config: remove extra extension files β
The commit title should be precise, and to the point but at the same time, it shouldn't be vague. All of the extra details should go in the description (
β¨ feat: add new feature β
β¨ feat: add sign up feature with forgot password and auth with Google β
β¨ feat: add sign up feature using OAuth β
β¨ feat: add sign up feature β
Following are some more examples:
π config: add .gitignore file
β»οΈ ref: move functions to helper.js
π¦ misc: add initial test cases
π¦ docs: update docs with v2.0 features
- You added
.yaml
file for GitHub Actions
β¨ config: add .yaml file for github actions
- You added some tests cases for the user interface
π¦ misc: add test cases for ui
- You moved some part of the code to components folder
β»οΈ ref: move pages code into components
- You updated the code that caused some breaking changes
π₯break: update sign-up api endpoints
- You made some changes to the user interface
π¨ style: update the auto pages
If you like the work, please give this repo a βοΈ and feel free to contribute to this project through issues, and pull requests.