> The "what it does" form is more useful if for some reason you're scanning commits trying to find the one that introduced some particular change. But that's no

> The "what it does" form is more useful if for some reason you're scanning commits trying to find the one that introduced some particular change. But that's not a use case I ever encounter. There are at least two use cases where I find it useful: 1. To review (recent) changes when you have no time to read full diffs but may hope that git commit messages will give a good idea what was changed since the previous review. There are many repos I follow and reading logs takes less time than diffs. 2. To find out when some change was made for which I know keywords to look in a message but not the code (and then I can check a diff to see the code). Why is indeed very important but a good commit messages can have booth: a short summary for what was changed and why.