Git rebase a branch onto master failed, how to resolve?

I’ve been working on a local copy of a remote git repo.
I created a branch on my local copy, let’s call it ‘my_branch’.
I’ve committed a few times on my_branch.

I recently pushed ‘my_branch’ to remote. However I didn’t know that someone else added a version to the remote master. So, I fetched it to my local master.

So…long story short, my local repo looks like this (I’m trying to use the diagraming convention here) .

 --C0--------------C7--  (local master)
       --C1-C2-C3--     (local my_branch)
              --C4-C5-C6--     (local sandbox_branch)

I want it to look like:

 --C0--------------C7--  (local master)
                       --C1'-C2'-C3'--     (local my_branch)
                              --C4'-C5'-C6'--     (local sandbox_branch)

I tried to rebase my_branch ONTO local master but I got this error message (I’m using a visual tool for git called GitX):

Rebase Failed!
There was an error rebasing HEAD with branch 'master'.

command: git rebase refs/heads/master

It seems that I cannot create a rebase-apply directory, and
I wonder if you are in the middle of patch application or another
rebase.  If that is not the case, please
    rm -fr /my_project_directory/.git/rebase-apply
and run me again.  I am stopping in case you still have something
valuable there.

What am I doing wrong? How should I handle this? If I were to do this on the command line what is the command to get me to the state in the diagram above?


BTW, I’m not in the middle of an application patch or another rebase…at least not intentional.
After I found out that remote was updated AFTER I pushed, I did a fetch. Could that have done anything to make GitX think that I’m in the middle of an application patch or another rebase?

I’ve also updated the diagram to be more accurate. There is a branch off of my_branch. I didn’t include it in the original question b/c I didn’t think that it would matter. I’m including just in case…


FYI…The master tree for ‘local’ and for ‘remote’ looks like the diagram that I drew, except it doesn’t have the sandbox_branch.

  • Git no space left on device
  • how to setup this git workflow?
  • How to avoid git rebase killing merge commits?
  • Unrecoverable git push?
  • Undo Git Rebase
  • Complex interactive rebase in one step?
  • How to move git branch up tree (reverse rebase)
  • git rebase for keeping most recent commit
  • One Solution collect form web for “Git rebase a branch onto master failed, how to resolve?”

    git rebase has found a .git/rebase-apply directory and so presumes that you might be in the middle of a rebase. This would have happened if there was a conflict during a previous rebase and the rebase was not finished; i.e. you did not run one of git rebase --abort, git rebase --skip or git rebase --continue (the last one after resolving the conflict).

    Anyway, it does not matter how you ended up in this state if you don’t think you ran git rebase at all. Simply rm -fr /my_project_directory/.git/rebase-apply as the help suggests and you should be able to do the rebase now.

    But wait. Since you say that you have already published your branch to the remote repository, you should not try to rebase master onto it. In fact, if your remote is set to deny non-fast-forward commits (which seems to be a generally recommended best practice), you’ll not even be able to push the rebase’d changes to your remote. In general, it is a bad practice to try to modify a commit (which is what git rebase does) after you have published it to a remote.

    Git Baby is a git and github fan, let's start git clone.