> Commits often touch files for completely arbitrary reasons, so the last commit tells you almost nothing. I can’t think of any case when somebody would need that particular information
You sir are using git in a very wrong way it seems. Its not dropbox, you get to decide and see exactly what changed and why. Not just do a `git add .; git commit; git push`
I think I can see what the author meant. It's not about doing `git add . && git commit`; it's about things like changing the signature of a utility function and touching all files which use it. Such a commit arguably doesn't tell you too much about the file itself. I disagree with the author that it happens often enough to make the "last commit which touched this file" not useful, though.
I think it would be safe to assume that the author knows pretty well how to use git and github: https://github.com/tonsky/
Probably, while his own commit messages seem to be consistent and informative, he spent too much time looking at repos of other people, where it is not so.
Since I frequently have the same feeling when exploring potential dependencies for my projects, so yes, changing the Github UI to accept the status quo seems more logical for me, than trying to reeducate all the developers in the world to follow the universal guidelines for commit messages sensibility.
You sir are using git in a very wrong way it seems. Its not dropbox, you get to decide and see exactly what changed and why. Not just do a `git add .; git commit; git push`