I too wish for this. Some people are really great at writing commit messages, most are not. But for even for the ones who write the best commit messages, often

I too wish for this. Some people are really great at writing commit messages, most are not. But for even for the ones who write the best commit messages, often their is a lot of discussion inside the actual MR which never makes it into git. GitLab and GitHub write a merge commit that can be used to get back to that discussion, but a git blame or bisect doesn't take you to the merge commit, which means you have to spend a fair amount of effort to get to the merge commit. Treating merges as a group would be amazing. Something but addressed in the article is how you deal with groups of groups of groups of merges. IE topic, feature, dev, master branches. It would be somewhat difficult to make the tooling graceful at ungrouping different levels of groups.