> I don't want to just see the final state of ours/theirs, but the changes that us/them did in order to get to those final states. I'm curious, would somethin

> I don't want to just see the final state of ours/theirs, but the changes that us/them did in order to get to those final states. I'm curious, would something like this help you better understand a complex merge? https://public.gitsense.com/insight/github?r=Microsoft/vscode#h%3Dgithub%26b%3Dgithub%3AMicrosoft%2Fvscode%3Ags_pr_40958%26q%3Ddiff%3Aa83a46d9a7356e955ed9a3dcc75193040588d35c...3cae8932ee764bba07624242fedb9bdbc4037073%26t%3Ddiffcommits https://public.gitsense.com/insight/github?r=Microsoft/vscod... If you click on the files in the pull request, you can see the diff and the changes on the source and target branches at once. You can also search for diffs on both branches at once, to quickly see how they were introduced. Disclaimer: I'm the creator behind GitSense