Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

git rebase --continue vs. new commit

If I run into merge errors, I usually solve the merge errors, add my files again and use git rebase --continue
to continue with pulling and pushing.

Now I had some time to take a deeper look into how git works and figured out, that it should be possible to create a new commit instead. I think, thats maybe a good idea to clarify that there were some merge errors and that they were solved manually.

So which one is recommed to use and what are their both advantages and disadvantages? Thanks in advance!

like image 350
julandi Avatar asked Oct 30 '22 14:10

julandi


1 Answers

Just use git rebase --continue. Resolving conflicts is an expected part of rebasing. You're throwing away the old commit that actually caused the conflict, so I don't see any benefit in recording its resolution separately.

like image 183
Matthew Strawbridge Avatar answered Nov 14 '22 00:11

Matthew Strawbridge