Are there any best practices around commit message content? So much is documented using Merge Requests / Pull Requests now, but that content lives outside the

Are there any best practices around commit message content? So much is documented using Merge Requests / Pull Requests now, but that content lives outside the git history. Is anyone moving info from Merge Requests into commit messages (stuff like peer review history, code review history, linkage between design and code)?