User feedback for commits introduced by Merge Requests
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.