Completion completed.
# On branch crtdev
You see, he does not say anything about what is happening in the recovery phase. Babaza is over. The only thing he says is that crtdev and origin/crtdev diverge, but this is exactly what is supposed to be said after rebase.
You did rebase crtdev on master . This means that you dropped the old crtdev story and crtdev it on master . However, origin/crtdev is a separate reflection and still points to an old story. Your story now looks something like this:
X--Y--Z...--master \ \ \ A'--B'--C'--D'--E'--F'--crtdev \ A--B--C--D--E--F--origin/crtdev
Changes A' - crtdev the same changes (without resolving the conflict) as A - origin/crtdev , but they are new changes. Since they also contain new changes from master and commit ID in git, this is a checksum of its contents.
Now , if no one is based on origin/crtdev , you just want to infer a new story. git push -f (branch names are the same, so no arguments are needed, the full command will be git push -f origin crtdev:crtdev ).
If, however, someone already used origin/crtdev , you did the wrong thing . You must undo the results of rebase ( git reset --hard origin/crtdev ) and merge . The problem is that if another branch-based work already exists, it will remain old based on it. Although you can reinstall it in the new version, it is very easy to forget and do something wrong and very confusing for an unsuspecting colleague.
Jan Hudec
source share