The use of Git for us Devs is something essential, whether in personal projects, open source with many people or an entire community.
Given that, it’s important that we use git commit properly. Having a coherent and standardized language helps everyone involved in the project to understand the changes that have occurred.
In the image above, we see how harmful a poorly commented commit can be, since we fail to understand the nature of the change that occurred and the context of it. In the long run, the effect is even more damaging, as the maintainability of the software suffers due to inconsistencies in the scope of these changes, and how they have affected the project in the past.
With that in mind, let’s talk a little about Conventional Commits Pattern.
What Is It?
Conventional Commits is a simple convention for commit messages, which follows a set of rules and helps projects to have an explicit and well-structured commit history.