In comparison to the graph git itself outputs, I find the one done by Sublime Merge misleading because parent lines are not drawn in accordance to the order specified by a merge commit, but in a way that makes more visual sense.
This is OK from the UI perspective, and normally the order is irrelevant, but where it matters, and where it breaks my flow, is when cherry-picking merges. Git expects an -m option specifying the index of the parent and until now I’ve always looked at the git graph to determine which index to use. Git log’s graph twists the merge commit if necessary so that the line linking the commit to its first parent is always on the left, and the one to the second parent is on the right (see screenshot for clarification).
Will this be implemented in the future? Thanks.
