0229b5d518
Running `git commit` before `git rebase --continue` is unnecessary when rebasing. Change-Id: I903ecfac7c7cc75d5a43fa665866589ae7373428
1.6 KiB
Resolving merge conflicts
If the change that you submitted has a merge conflict, you need to
manually resolve it using git rebase.
Rebasing is used to integrate changes from one branch into another to resolve conflicts when multiple commits happen on the same file.
Warning
Never do a rebase on public (master) branches.
You submit a change.
Somebody else submits a change and that change merges. Now your change has a merge conflict.
Update your local repository:
$ git remote update $ git pull --ff-only origin masterDownload your change:
$ git review -d $PARENT_CHANGE_NUMBERRebase your change:
$ git rebase origin/masterResolve conflicts manually:
Conflicts are marked in a file with clear line breaks:
<<<<<<< HEAD Second line. ======= Third line. >>>>>>> feature/topic branch.<<<<<<<: Indicates the start of the lines that had a merge conflict.
=======: Indicates separation of the two conflicting changes.
>>>>>>>: Indicates the end of the lines that had a merge conflict.
You need to resolve a conflict by manually editing the file. You also need to delete the '<<<<<<<', '=======', and'>>>>>>>' in the file.
Add the files to the stage:
$ git add $FILENAMEComplete the rebase process:
$ git rebase --continueSend the rebased patch again for review:
$ git review