⭐ How to Write Good Commit Messages▶️
feat Commits, that
adds or
remove a new feature
▶️
fix Commits, that
fixes a bug
▶️
refactor Commits, that
rewrite/restructure your code, however does not change any API behaviour
- - - - - - - - - - - - - - - - - - - - - - - -▶️
perf Commits are special refactor
commits, that improve performance
▶️
style Commits, that do not affect the meaning (white-space,
formatting, missing semi-colons, etc)
▶️
test Commits, that add missing tests or correcting existing tests
- - - - - - - - - - - - - - - - - - - - - - - -docs: Add Git commit message convention guidelines 😎
▶️
docs Commits, that affect
documentation only
▶️
build Commits, that affect build components like
build tool, ci pipeline, dependencies, project version, ...
▶️
ops Commits, that affect operational components like infrastructure,
deployment, backup, recovery, ...
▶️
chore Miscellaneous commits e.g. modifying .gitignore
References 🔥
https://www.conventionalcommits.org/en/v1.0.0/Next Post: git branch naming convention🎤