Good commit messages serve at least three important purposes:
- To speed up the reviewing process.
- To find out what changed in a range of commits (e.g. for a release note).
- To help the future maintainers, say five years into the future, to find out why a particular change was made to the code or why a specific feature was added.
Structure your commit message like this:
