Merge conflict resolution

When there’s a merge conflict in Git, junk like the following is inserted into the conflicting files. Three questions:

  1. How do you read these annotations?
  2. What are some strategies to use when fixing these merge conflicts?
  3. Is there a GUI tool for Mac that knows how to read these files and display the two versions side-by-side to make it easier to fix the problem?

enter image description here

  • Git doesn't show how many commits ahead of origin I am, and I want it to
  • Is it necessary to clean the Linux kernel source tree after each bisection step?
  • Git confused when merging an update into my subtree
  • How git clone actually works
  • What's the purpose of forking a git repo?
  • Using Git to track mysql schema - some questions
  • Note: In case it’s relevant, I am using GitHub’s Mac GUI client.

  • Git diff -w ignore whitespace only at start & end of lines
  • How to prevent git vimdiff from opening files as read-only?
  • git status takes too long
  • finding first commit of a file in git
  • Linking code coverage to version control
  • Git Bash is displaying strange characters on Windows 7
  • 4 Solutions collect form web for “Merge conflict resolution”

    Everything between <<<<<< and ====== comes from the HEAD revision, which is the committed state before starting the merge operation (git merge will complain if the tree is dirty, so it should be equivalent to your working directory).

    The parts between ====== and >>>>>> come from the version being merged. The text after the >>>>>> is the comment of the commit that introduced the conflicting change.

    That there is a conflict marker means that the base version of this part of the file is different from both “new” versions. The base version (last common ancestor) is not shown.

    If you want a more comfortable merge and have a GUI available, I suggest you take a look at kdiff3.

    There’s now a better solution than trying to read the gibberish markers that Git inserts into your files. Kaleidoscope 2, Black Pixel’s second release of their diff tool, is now also a merge tool. It’s not free, but it works beautifully.

    After you install Kaleidoscope 2, it’s really simple to integrate with Git. Open Kaleidoscope and from the Menu Bar choose Kaleidoscope > Integration…

    Kaleidoscope's Integration menu option.

    Then you’ll see this window. Simply choose Git from the left nav and then install the ksdiff command-line tool and then make Kaleidoscope Git’s default diff and merge tool.

    Kaleidoscope's Git Integration dialog.

    Finally, once you have a merge conflict in Git, simply go to the command line and execute git mergetool. Now the conflict is easy to read. Enjoy.

    Kaleidoscope sane view for merge conflicts.

    <<<< HEAD #Where the conflict starts
    #Previous Revision
    ========== # The point where things look iffy
    #Things that changed
    >>>>> New Commit # Point where the conflict ends

    Mac’s Xcode comes with FileMerge which can be accessed on the command line with opendiff.

    git mergetool -t opendiff

    You can configure a (graphical) merge tool and use that tool to do the conflict resolution.

    Also have a look at the git mergetool command – if you have one of the pre-defined tools installed or have configured some other tool, it will open up the tool for resolution

    If you are interested in GUI tools, you need not worry about what the notations really mean, as the GUI tool will help you to easily make the resolutions. Just understand that the parts marked with ===== and >>>>> are the conflict sections.

    Git Baby is a git and github fan, let's start git clone.