I would also add, that it's good to have task/issue number (if it exists), first in the commit header, like ASD-123 Fix main window not being displayed. That way you can quickly see which commits are related to each other in git log.
RE: Writing efficient commit messages; software projects, and Utopian
You are viewing a single comment's thread from:
Writing efficient commit messages; software projects, and Utopian
Good point. We practice this also in our workflow at the company.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit