RE: Writing efficient commit messages; software projects, and Utopian
It's an honor to moderate the first #iamutopian post. We don't really have an appropriate scoring format for these posts, of course, as they are a new and unique thing we're doing. Therefore, the score won't be reflective of the post's quality.
This is a very useful post, and one that I hope future contributors to your category will read and refer to.
I do have a couple of comments, because I always have a couple of comments.
On the style and grammar side, the post is generally quite good, but there are small issues.
For instance, "we have different kind of metrics" should be "we have a different kind of metrics"
"speed-up code reviewing process" should be "speed up the code reviewing process." Note that I removed the hyphen from "speed up" as well.
On the content side, I would have loved to have seen your own explanation of what makes a good commit message, not the one Linus wrote. I would have also liked "some bad examples" to include some actual bad examples.
Thank you for your contribution and for being the first to brave the waters of #iamutopian.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]
Thank you for the review and great feedback.
Thank you for your review, @didic!
So far this week you've reviewed 15 contributions. Keep up the good work!
i hpe in the chage life .........