User feedback for commits introduced by Merge Requests
Quoting @muxator on mercurial/hg-git!38 (merged):
There is probably a UI bug in Heptapod. Before merging, I rebased this PR to keep the history linear. Yet the web UI showed that merging this PR would have created 3 commits: 2 normal ones and a merge commit. Upon merging, Heptapod did the right thing and no merge commit was created. This could have been much disorienting to a newcomer.
I've actually known about this for a long time, but never got around filing it properly.
In the Git case, the merge commit would be systematic with the :merge
merge method.
It's probably harder to fix than it looks, depending how much of that display is implemented in JavaScript. Also, it's possible that the piece of code handling the display wouldn't have access to the information whether the MR is actually linear or not. In that case, I suppose being less definitive in the message would be the best thing to do.