3 # Copyright (c) 2005 Junio C Hamano.
6 USAGE='[--onto <newbase>] <upstream> [<branch>]'
7 LONG_USAGE='git-rebase replaces <branch> with a new branch of the
8 same name. When the --onto option is provided the new branch starts
9 out with a HEAD equal to <newbase>, otherwise it is equal to <upstream>
10 It then attempts to create a new commit for each commit from the original
11 <branch> that does not exist in the <upstream> branch.
13 It is possible that a merge failure will prevent this process from being
14 completely automatic. You will have to resolve any such merge failure
15 and run git rebase --continue. Another option is to bypass the commit
16 that caused the merge failure with git rebase --skip. To restore the
17 original <branch> and remove the .dotest working files, use the command
18 git rebase --abort instead.
20 Note that if <branch> is not specified on the command line, the
21 currently checked out branch is used. You must be in the top
22 directory of your project to start (or continue) a rebase.
24 Example: git-rebase master~1 topic
26 A---B---C topic A'\''--B'\''--C'\'' topic
28 D---E---F---G master D---E---F---G master
33 When you have resolved this problem run \"git rebase --continue\".
34 If you would prefer to skip this patch, instead run \"git rebase --skip\".
35 To restore the original branch and stop rebasing run \"git rebase --abort\".
38 while case "$#" in 0) break ;; esac
42 diff=$(git-diff-files)
44 ?*) echo "You must edit all merge conflicts and then"
45 echo "mark them as resolved using git update-index"
49 git am --resolved --3way --resolvemsg="$RESOLVEMSG"
53 git am -3 --skip --resolvemsg="$RESOLVEMSG"
57 [ -d .dotest ] || die "No rebase in progress?"
58 git reset --hard ORIG_HEAD
63 test 2 -le "$#" || usage
77 # Make sure we do not have .dotest
83 It seems that I cannot create a .dotest directory, and I wonder if you
84 are in the middle of patch application or another rebase. If that is not
85 the case, please rm -fr .dotest and run me again. I am stopping in case
86 you still have something valuable there.'
90 # The tree must be really really clean.
91 git-update-index --refresh || exit
92 diff=$(git-diff-index --cached --name-status -r HEAD)
99 # The upstream head must be given. Make sure it is valid.
101 upstream=`git rev-parse --verify "${upstream_name}^0"` ||
102 die "invalid upstream $upstream_name"
104 # If a hook exists, give it a chance to interrupt
105 if test -x "$GIT_DIR/hooks/pre-rebase"
107 "$GIT_DIR/hooks/pre-rebase" ${1+"$@"} || {
108 echo >&2 "The pre-rebase hook refused to rebase."
113 # If the branch to rebase is given, first switch to it.
117 git-checkout "$2" || usage
120 branch_name=`git symbolic-ref HEAD` || die "No current branch"
121 branch_name=`expr "z$branch_name" : 'zrefs/heads/\(.*\)'`
124 branch=$(git-rev-parse --verify "${branch_name}^0") || exit
126 # Make sure the branch to rebase onto is valid.
127 onto_name=${newbase-"$upstream_name"}
128 onto=$(git-rev-parse --verify "${onto_name}^0") || exit
130 # Now we are rebasing commits $upstream..$branch on top of $onto
132 # Check if we are already based on $onto, but this should be
133 # done only when upstream and onto are the same.
134 if test "$upstream" = "$onto"
136 mb=$(git-merge-base "$onto" "$branch")
137 if test "$mb" = "$onto"
139 echo >&2 "Current branch $branch_name is up to date."
144 # Rewind the head to "$onto"; this saves our current head in ORIG_HEAD.
145 git-reset --hard "$onto"
147 # If the $onto is a proper descendant of the tip of the branch, then
148 # we just fast forwarded.
149 if test "$mb" = "$onto"
151 echo >&2 "Fast-forwarded $branch to $newbase."
155 git-format-patch -k --stdout --full-index "$upstream"..ORIG_HEAD |
156 git am --binary -3 -k --resolvemsg="$RESOLVEMSG"