Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Git Merge Conflict (UU): How do I resolve conflict without adding file to next commit?

Tags:

git

merge

How do I resolve a UU (merge conflict) without adding that file to the next commit.

For example, I just cherry picked a commit to another branch and there were merge issues. I solved the merge issue and want UU readme.txt changed to M readme.txt but it not be added to the next commit I make.

Thanks

like image 263
KRB Avatar asked Sep 22 '11 15:09

KRB


People also ask

Do I need to commit after merge conflict?

When there is a conflict during a merge, you have to finish the merge commit manually. It sounds like you've done the first two steps, to edit the files that conflicted and then run git add on them to mark them as resolved. Finally, you need to actually commit the merge with git commit .


1 Answers

I don't know what version of git you were using back in '11, but right now I'm on 1.7.7.4.

It appears to me that doing an add to mark the conflict resolved does add the file to the stage; so my approach is:

git add <filename>
git reset HEAD <filename>

You could also create a custom git command that does this for you. I created an executable file named git-resolve (no extension) in a directory on my path (I like to put stuff like this in ~/.bin) and put this in it:

git add $@
git reset HEAD $@

Then from the command line, after I've resolved my conflicts, I can do:

$ git resolve <filename>
like image 57
Adam Tuttle Avatar answered Oct 04 '22 12:10

Adam Tuttle