If you use Bitbucket, GitHub and/or GitLab, you would know that, when viewing a merge commit
through their commit's tool, you can easily tell what was changed, like so:
merge commit b2375af33 from atlassian/aui
merge commit 35ceb66a from atom/atom
merge commit c9a4626 from gitlab-org/gitlab-ce
but what they can't tell you, well not with ease, is:
- who's changes were merged
- when were these changes made
- and what were the reasons for these changes
but GitSense can.
With GitSense, you just have to click the merge analysis link,
and it will let you know who's changes were merged and when they were made.
To answer why, click the right arrow, that is located below the contributor's avatar, to view their commit message
To analyze the merged files, switch to the "Change analytics" tab, to see what files were changed and how frequently.
And to see what these changes were, launch the diffs browser
which provides an easy wasy, to iterate through one or a thousand changes.
So as you can see, when it comes to merge commits, GitSense makes it very easy to put these changes into context.
And if you haven't already done so, make sure to checkout our previous blog post, to learn more about how GitSense is reimagining Git browsing.