There are plenty of articles on writing a proper commit message. But the problem is more profound than the wrong messages. The core problem is that developers think about git as a code delivery tool, not collaboration. With this article, I want to describe the value of meaningful commit messages in general, not the essence of some specific rules.
There are seven more or less standard rules: https://chris.beams.io/posts/git-commit/#seven-rules.
Additionally, many teams have a standard to mention an issue id, but it is used mostly for integration with your issue manager. It can not be a rule itself because the issue…