Simple tool to accept theirs or accept mine on a whole file using git

Question

I don t want a visual merge tool  and I also don t want to have to vi the conflicted file and manually choose the between HEAD  mine  and the imported change  theirs    Most of the time I either want all of their changes or all of mine   Commonly this is because my change made it upsteam and is coming back to me through a pull  but may be slightly modified in various places   Is there a command line tool which will get rid of the conflict markers and choose all one way or another based on my choice   Or a set of git commands which I can alias myself to do each one     accept mine alias am  some sequence of commands  alias at  some other sequence of commands    Doing this is rather annoying  For  accept mine  I have tried    randy sabotage   linus   git merge test-branch Auto-merging Makefile CONFLICT  content   Merge conflict in Makefile Automatic merge failed  fix conflicts and then commit the result   randy sabotage   linus   git checkout Makefile  error  path  Makefile  is unmerged  andy sabotage   linus   git reset --hard HEAD Makefile  fatal  Cannot do hard reset with paths    How am I supposed to get rid of these change markers   I can do    git reset HEAD Makefile  rm Makefile  git checkout Makefile   But this seems rather round about  there must be a better way   And at this point  I m not sure if git even thinks the merge happened  so I don t think this necessarily even works   Going the other way  doing  accept theirs  is equally messy  The only way I can figure it out is do   git show test-branch Makefile  gt  Makefile  git add Makefile    This also gives me a messed up commit message  which has Conflicts  Makefile in it twice   Can someone please point out how to do the above two actions in a simpler way   Thanks

User · Answer

Try this   To accept theirs changes  git merge --strategy-option theirs   To accept yours  git merge --strategy-option ours

User · Answer

The ideal situation for resolving conflicts is when you know ahead of time which way you want to resolve them and can pass the -Xours or -Xtheirs recursive merge strategy options   Outside of this I can see three scenarious   You want to just keep a single version of the file  this should probably only be used on unmergeable binary files  since otherwise conflicted and non-conflicted files may get out of sync with each other   You want to simply decide all of the conflicts in a particular direction  You need to resolve some conflicts manually and then resolve all of the rest in a particular direction   To address these three scenarios you can add the following lines to your  gitconfig file  or equivalent    merge    conflictstyle   diff3  mergetool getours    cmd   git-checkout --ours   MERGED    trustExitCode   true  mergetool mergeours    cmd   git-merge-file --ours   LOCAL    BASE    REMOTE  -p  gt    MERGED    trustExitCode   true  mergetool keepours    cmd   sed -i    -e     lt  lt  lt  lt  lt  lt  lt  d  -e                gt  gt  gt  gt  gt  gt  gt  d    MERGED    trustExitCode   true  mergetool gettheirs    cmd   git-checkout --theirs   MERGED    trustExitCode   true  mergetool mergetheirs    cmd   git-merge-file --theirs   LOCAL    BASE    REMOTE  -p  gt    MERGED    trustExitCode   true  mergetool keeptheirs    cmd   sed -i    -e     lt  lt  lt  lt  lt  lt  lt             d  -e     gt  gt  gt  gt  gt  gt  gt  d    MERGED    trustExitCode   true  The get ours theirs  tool just keeps the respective version of the file and throws away all of the changes from the other version  so no merging occurs   The merge ours theirs  tool re-does the three way merge from the local  base  and remote versions of the file  choosing to resolve conflicts in the given direction   This has some caveats  specifically  it ignores the diff options that were passed to the merge command  such as algorithm and whitespace handling   does the merge cleanly from the original files  so any manual changes to the file are discarded  which could be good or bad   and has the advantage that it cannot be confused by diff markers that are supposed to be in the file  The keep ours theirs  tool simply edits out the diff markers and enclosed sections  detecting them by regular expression   This has the advantage that it preserves the diff options from the merge command and allows you to resolve some conflicts by hand and then automatically resolve the rest   It has the disadvantage that if there are other conflict markers in the file it could get confused  These are all used by running git mergetool -t  get merge keep  ours theirs    lt filename gt   where if  lt filename gt  is not supplied it processes all conflicted files  Generally speaking  assuming you know there are no diff markers to confuse the regular expression  the keep  variants of the command are the most powerful   If you leave the mergetool keepBackup option unset or true then after the merge you can diff the   orig file against the result of the merge to check that it makes sense   As an example  I run the following after the mergetool just to inspect the changes before committing  for f in  find   -name    orig    do vimdiff  f   f  orig   done  Note  If the merge conflictstyle is not diff3 then the            pattern in the sed rule needs to be            instead

User · Answer

Based on kynan s answer  here are the same aliases  modified so they can handle spaces and initial dashes in filenames   accept-ours     f       -z           amp  amp  set -      git checkout --ours --         git add -u --            f  accept-theirs     f       -z           amp  amp  set -      git checkout --theirs --         git add -u --            f

User · Answer

The solution is very simple  git checkout  lt filename gt  tries to check out file from the index  and therefore fails on merge  What you need to do is  i e  checkout a commit   To checkout your own version you can use one of  git checkout HEAD --  lt filename gt   or git checkout --ours --  lt filename gt    Warning   If you are rebasing  --ours and --theirs are swapped   or git show  2  lt filename gt   gt   lt filename gt     stage 2 is ours   To checkout the other version you can use one of  git checkout test-branch --  lt filename gt   or git checkout --theirs --  lt filename gt   or git show  3  lt filename gt   gt   lt filename gt     stage 3 is theirs   You would also need to run  add  to mark it as resolved  git add  lt filename gt

User · Answer

Based on Jakub s answer you can configure the following git aliases for convenience   accept-ours     f     git checkout --ours --       -      git add -u       -         f  accept-theirs     f     git checkout --theirs --       -      git add -u       -         f    They optionally take one or several paths of files to resolve and default to resolving everything under the current directory if none are given   Add them to the  alias  section of your    gitconfig or run  git config --global alias accept-ours   f     git checkout --ours --      -     git add -u      -        f  git config --global alias accept-theirs   f     git checkout --theirs --      -     git add -u      -        f

[git] Simple tool to 'accept theirs' or 'accept mine' on a whole file using git

Examples related to git

Examples related to merge