You know the saying “If you keep looking at the past, you’ll miss the future”? Well in the context of coding and working with Git, that’s not the case.  Your commit history plays a huge role in the future of the open source projects that you contribute to, and

freeCodeCamp is a nonprofit organization offering free online coding courses and programming tutorials, covering topics such as web development, data science, and machine learning. Learners can gain practical coding skills, build real-world projects, and earn certifications to advance their careers in tech.

freeCodeCamp

Learn how to write effective commit messages that project maintainers will appreciate. Avoid vague messages and instead mention the type of change and summarize the details. Consider adding a description for more clarity and understanding. Writing good commit messages is crucial for communicating contributions.

How to Write Commit Messages that Project Maintainers Will Appreciate

<a href="http://commitlint.io" target="_blank" rel="noopener nofollow">commitlint.io</a>

You can use the conventional commits extension for VS Code to do that.

Nice Article.
The Conclusion :
To write a good commit is by three steps.
step 1:
Mention the type of the commit whether it was ‘fix’ or ‘feat’ and so on …
And there are almost 4 types and the types is :
feat : when adding something
docs : when applying some changes on the project’s document
fix : when fixing a bug
chore : for everyday work .
step 2 :
summarize the change
step 3 (optional) :
add a description .

I have had to write numerous commit messages over the years. This blog resonates with me because it emphasizes the importance of clear and concise commit messages, which is something I have always advocated for in my team. I have seen firsthand how poor commit messages can lead to confusion and slow down the development process, so I appreciate the author’s efforts to educate readers on this topic.