How to resolve ALL conflicts using HEAD, with any mergetool

So for some reason I’m getting a lot of conflicts with a new merged hotfix. The file that was actually [manually] changed has no conflict.
All the conflicts are in files that were untouched during the fix and apparently its an issue with whitespaces. I’ll try to figure that problem later but now I need to merge the hotfix and deploy.

How can I resolve ALL conflicts to use the HEAD version? I don’t want to go file by file. Yes, I know its a bad practice but the conflicts are all whitespaces and I know HEAD is correct — passing all tests and running fine in production.

  • Git SVN and merging branches
  • How git works when two peers push changes to same remote simultaneously
  • How can I preserve line endings when I check out a single file to a different location with git?
  • Track the same files in multiple repositories
  • Running a Git build inside a ClearCase View in tcsh
  • How to fetch all git branches
  • Any ideas?

    I’m using OSX.

  • Specific RSA keys per git repo
  • Git updating a stale local repo
  • How to add private github repository as Composer dependency
  • Git having different branches push to different remote repos
  • how to delete files in the remote repository?
  • git add -p in Windows Git Shell, child_info_fork::abort
  • 2 Solutions collect form web for “How to resolve ALL conflicts using HEAD, with any mergetool”

    git merge -Xours origin/master
    

    will do a merge with origin/master (the same thing that git pull origin master does) and will resolve any conflicts by taking the versions from your local branch.

    If you’re already part-way through the bad merge, you can reset everything to the head first with git reset --hard HEAD.

    In that case, you should do

    git reset --hard HEAD
    git merge -Xours origin/master
    

    And that should fix your problem!

    (also worth mentioning, -Xtheirs will do the same thing, but take the upstream version in any conflicts.)


    Also, most likely the conflicts are because the upstream version is using windows-style line endings, and whatever program you edited the files in on your local machine is using mac-style or linux-style line endings.

    There are options you can set in git to always commit windows-style or linux-style line endings, but always checkout mac-style or linux-style in your working directory.

    See this link for more info:
    https://help.github.com/articles/dealing-with-line-endings

    I would:

    $ git checkout master   # or where ever you want to merge the hotfix into
    $ git merge --no-commit -Xours <hotfix-branch>
    $ git status    # make sure the only change is the file you wanted
    $ git diff      # make sure they changes are what you wanted
    $ git commit -m "<your merge message"
    

    This will use the default recursive strategy pull in any non-conflicting files, but it will resolve any conflicting files by using simply using the master/HEAD version. The docs:

    $ git merge --help
    ....
    
       recursive
           ... This is the default merge strategy when pulling or merging one branch.
    
           The recursive strategy can take the following options:
    
           ours
               This option forces conflicting hunks to be auto-resolved cleanly
               by favoring our version. Changes from the other tree that do not
               conflict with our side are reflected to the merge result. ....
    
    Git Baby is a git and github fan, let's start git clone.