HOW TO WRITE COMMIT MESSAGES THAT MAINTAINERS WILL APPRECIATE

Summary from the TLDR Web Dev newsletter

Commit messages play a significant role in the future of open source projects. A good commit message should clearly state the type of change, summarize the change, and optionally include a detailed description. Using an example, this article demonstrates how to transform a vague commit message into one that is informative and useful to maintainers, following the steps of specifying the commit type, summarizing the change, and adding an optional detailed description.