Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 380
    • Issues 380
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGitTortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #2469
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

Support reviewing merge commits (git show merge-commit)

By yves.goer... on March 21, 2015 23:28 (imported from Google Code)


It seems TortoiseGit does not support merge commits in a special way. I've learned about how to review them in this article: (interesting read!)
http://haacked.com/archive/2014/02/21/reviewing-merge-commits/
The point is that when a merge has conflicts, only those conflict resolution changes need further review, or might be interesting otherwise. Automatic, unchanged merges have already been reviewed and should be just fine.

GitHub only shows the complete diff compared to both parents, not what changes the merge commit introduced itself over the two parents. Reading all of it would mean to review it a second time.

TortoiseGit doesn't show any special output. In the log window, I just get the changed files for both parents and can see the same full differences. I haven't found any context menu command to give me a smarter output.

Only the command 'git show <merge commit hash>' will print a diff of the changes that the merge has introduced itself. I'm interested in a GUI way to access this information. Especially because Git can't use the Windows console window. (It states the terminal is broken, and indeed it is. I can't scroll at all in the less-like viewer.) Piping the output through 'cat' to get the plain output is not very well readable either (line wrapping, no colours).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking