Commit messages (out-of-band) tie this information to the specific time when the change was made. They also don't clutter the code up.
Comments (in-band) tie this information to the specific place where the change was made. If overused, they make the code harder to read.
Commits can get lost in the noise, though blame and bisect can help find them. Comments can get stale and cause more confusion than assistance.
Honestly, if we spent more time reviewing and revising each other's code than just writing it, then comments (combined with refactoring for readability) would probably be the better solution. But that would slow down development. If you're going fast or lean, then relying on commit messages is better than nothing at all or fired-and-forgotten comments.
Commit numbers are an API and it's frustrating when I write something like "Fixed in commit xyz" or "Broken in commit xyz" or "Tested manually in xyz" and then after a rebase (Not a private rebase I asked for, but part of the CI routine), my comment makes no sense and Github says "We can't find that commit". You can paste it in manually but the context is lost, it's not in `git log --graph` anymore.
Is that supposed to be a good or even useful thing?