As a Developers(and not just us), is very important to know how to write good commit messages.
Where the important of it? I know, I know You maybe read or listen one or more times things like: -Help you organizing your commit history -Allow your team where you change something -Your team can know what changes you had made
Let’s look down on those points from the last to the first one:
“Your team can know what changes you had made” With a good commit you will let people know, what exactly you had change, wich new feature your add, wich bug you solve.
“Allow your team where you change something” One of the powers of commit messages. I already know, from the commit message, what’s new and I also can know wich files where updated in the commit? Yes!
“Help you organizing your commit history” Yes, it really helps on that. How? By having good commit messages, your commit history becomes more, pretty, something good to look at and easy to see on time where you done something.
You get here, congrats! Now go make your commit messages, and your life, looks prettier.
Look at this post:<a href="https://dev.to/sheraz4194/good-commit-vs-bad-commit-best-practices-for-git-1plc" target="_blank" rel="noopener nofollow">https://dev.to/sheraz4194/good-commit-vs-bad-commit-best-practices-for-git-1plc</a>
#NoMoreBadCommits

The official Open Source daily.dev Squad. 

Open Source

The importance of writing good commit messages is emphasized for developers. Good commit messages help organize commit history, inform team members about changes, and specify the details of features or bug fixes. Improving your commit messages can make your development process more efficient and your project history easier to read.

Good Commit vs Bad Commit

Pretty neat article. I read the DEV post and I always thought maybe adding an extra change in the same commit would be beneficial but I can see how it can easily become cluttered if you do that for every commit change you do