Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.14.1 → 2.14.2 no changes
- 2.14.0 08/04/17
- 2.13.5 → 2.13.6 no changes
- 2.13.4 08/01/17
- 2.13.1 → 2.13.3 no changes
- 2.13.0 05/09/17
- 2.12.1 → 2.12.5 no changes
- 2.12.0 02/24/17
- 2.9.4 → 2.11.4 no changes
- 2.9.3 08/12/16
- 2.9.1 → 2.9.2 no changes
- 2.9.0 06/13/16
- 2.8.1 → 2.8.6 no changes
- 2.8.0 03/28/16
- 2.6.5 → 2.7.6 no changes
- 2.6.4 12/08/15
- 2.6.3 no changes
- 2.6.2 10/16/15
- 2.6.1 no changes
- 2.6.0 09/28/15
- 2.4.4 → 2.5.6 no changes
- 2.4.3 06/05/15
- 2.4.1 → 2.4.2 no changes
- 2.4.0 04/30/15
- 2.3.6 → 2.3.10 no changes
- 2.3.5 03/31/15
- 2.2.1 → 2.3.4 no changes
- 2.2.0 11/26/14
- 2.1.3 → 2.1.4 no changes
- 2.1.2 09/30/14
git-rebase [-i | --interactive] [-v | --verbose] [-m | --merge] [-s <strategy> | --strategy=<strategy>] [-C<n>] [ --whitespace=<option>] [-p | --preserve-merges] [--onto <newbase>] <upstream> [<branch>] git-rebase --continue | --skip | --abort
If <branch> is specified, git-rebase will perform an automatic
git checkout <branch> before doing anything else. Otherwise
it remains on the current branch.
All changes made by commits in the current branch but that are not
in <upstream> are saved to a temporary area. This is the same set
of commits that would be shown by
git log <upstream>..HEAD.
The current branch is reset to <upstream>, or <newbase> if the
--onto option was supplied. This has the exact same effect as
git reset --hard <upstream> (or <newbase>).
The commits that were previously saved into the temporary area are then reapplied to the current branch, one by one, in order. Note that any commits in HEAD which introduce the same textual changes as a commit in HEAD..<upstream> are omitted (i.e., a patch already accepted upstream with a different commit message or timestamp will be skipped).
It is possible that a merge failure will prevent this process from being
completely automatic. You will have to resolve any such merge failure
git rebase --continue. Another option is to bypass the commit
that caused the merge failure with
git rebase --skip. To restore the
original <branch> and remove the .dotest working files, use the command
git rebase --abort instead.
Assume the following history exists and the current branch is "topic":
A---B---C topic / D---E---F---G master
From this point, the result of either of the following commands:
git-rebase master git-rebase master topic
A'--B'--C' topic / D---E---F---G master
The latter form is just a short-hand of
git checkout topic
git rebase master.
If the upstream branch already contains a change you have made (e.g.,
because you mailed a patch which was applied upstream), then that commit
will be skipped. For example, running
git-rebase master on the
following history (in which A' and A introduce the same set of changes,
but have different committer information):
A---B---C topic / D---E---A'---F master
will result in:
B'---C' topic / D---E---A'---F master
Here is how you would transplant a topic branch based on one
branch to another, to pretend that you forked the topic branch
from the latter branch, using
First let’s assume your topic is based on branch next. For example feature developed in topic depends on some functionality which is found in next.
o---o---o---o---o master \ o---o---o---o---o next \ o---o---o topic
We would want to make topic forked from branch master, for example because the functionality topic branch depend on got merged into more stable master branch, like this:
o---o---o---o---o master | \ | o'--o'--o' topic \ o---o---o---o---o next
We can get this using the following command:
git-rebase --onto master next topic
Another example of --onto option is to rebase part of a branch. If we have the following situation:
H---I---J topicB / E---F---G topicA / A---B---C---D master
then the command
git-rebase --onto master topicA topicB
would result in:
H'--I'--J' topicB / | E---F---G topicA |/ A---B---C---D master
This is useful when topicB does not depend on topicA.
A range of commits could also be removed with rebase. If we have the following situation:
then the command
git-rebase --onto topicA~5 topicA~3 topicA
would result in the removal of commits F and G:
This is useful if F and G were flawed in some way, or should not be part of topicA. Note that the argument to --onto and the <upstream> parameter can be any valid commit-ish.
In case of conflict, git-rebase will stop at the first problematic commit and leave conflict markers in the tree. You can use git diff to locate the markers (<<<<<<) and make edits to resolve the conflict. For each file you edit, you need to tell git that the conflict has been resolved, typically this would be done with
git add <filename>
After resolving the conflict manually and updating the index with the desired resolution, you can continue the rebasing process with
git rebase --continue
Alternatively, you can undo the git-rebase with
git rebase --abort
Starting point at which to create the new commits. If the --onto option is not specified, the starting point is <upstream>. May be any valid commit, and not just an existing branch name.
Upstream branch to compare against. May be any valid commit, not just an existing branch name.
Working branch; defaults to HEAD.
Restart the rebasing process after having resolved a merge conflict.
Restore the original branch and abort the rebase operation.
Restart the rebasing process by skipping the current patch.
- -m, \--merge
Use merging strategies to rebase. When the recursive (default) merge strategy is used, this allows rebase to be aware of renames on the upstream side.
- -s <strategy>, \--strategy=<strategy>
Use the given merge strategy; can be supplied more than once to specify them in the order they should be tried. If there is no
-soption, a built-in list of strategies is used instead (
git-merge-recursivewhen merging a single head,
git-merge-octopusotherwise). This implies --merge.
- -v, \--verbose
Display a diffstat of what changed upstream since the last rebase.
Ensure at least <n> lines of surrounding context match before and after each change. When fewer lines of surrounding context exist they all must match. By default no context is ever ignored.
This flag is passed to the
git-applyprogram (see git-apply) that applies the patch.
- -i, \--interactive
Make a list of the commits which are about to be rebased. Let the user edit that list before rebasing. This mode can also be used to split commits (see SPLITTING COMMITS below).
- -p, \--preserve-merges
Instead of ignoring merges, try to recreate them. This option only works in interactive mode.
This can only resolve two heads (i.e. the current branch and another branch you pulled from) using 3-way merge algorithm. It tries to carefully detect criss-cross merge ambiguities and is considered generally safe and fast.
This can only resolve two heads using 3-way merge algorithm. When there are more than one common ancestors that can be used for 3-way merge, it creates a merged tree of the common ancestors and uses that as the reference tree for the 3-way merge. This has been reported to result in fewer merge conflicts without causing mis-merges by tests done on actual merge commits taken from Linux 2.6 kernel development history. Additionally this can detect and handle merges involving renames. This is the default merge strategy when pulling or merging one branch.
This resolves more than two-head case, but refuses to do complex merge that needs manual resolution. It is primarily meant to be used for bundling topic branch heads together. This is the default merge strategy when pulling or merging more than one branches.
This resolves any number of heads, but the result of the merge is always the current branch head. It is meant to be used to supersede old development history of side branches.
This is a modified recursive strategy. When merging trees A and B, if B corresponds to a subtree of A, B is first adjusted to match the tree structure of A, instead of reading the trees at the same level. This adjustment is also done to the common ancestor tree.
When you rebase a branch, you are changing its history in a way that will cause problems for anyone who already has a copy of the branch in their repository and tries to pull updates from you. You should understand the implications of using git rebase on a repository that you share.
When the git rebase command is run, it will first execute a "pre-rebase" hook if one exists. You can use this hook to do sanity checks and reject the rebase if it isn’t appropriate. Please see the template pre-rebase hook script for an example.
Upon completion, <branch> will be the current branch.
Rebasing interactively means that you have a chance to edit the commits which are rebased. You can reorder the commits, and you can remove them (weeding out bad or otherwise unwanted patches).
The interactive mode is meant for this type of workflow:
have a wonderful idea
hack on the code
prepare a series for submission
where point 2. consists of several instances of
finish something worthy of a commit
realize that something does not work
Sometimes the thing fixed in b.2. cannot be amended to the not-quite perfect commit it fixes, because that commit is buried deeply in a patch series. That is exactly what interactive rebase is for: use it after plenty of "a"s and "b"s, by rearranging and editing commits, and squashing multiple commits into one.
Start it with the last commit you want to retain as-is:
git rebase -i <after-this-commit>
An editor will be fired up with all the commits in your current branch (ignoring merge commits), which come after the given commit. You can reorder the commits in this list to your heart’s content, and you can remove them. The list looks more or less like this:
pick deadbee The oneline of this commit pick fa1afe1 The oneline of the next commit ...
The oneline descriptions are purely for your pleasure;
not look at them but at the commit names ("deadbee" and "fa1afe1" in this
example), so do not delete or edit the names.
By replacing the command "pick" with the command "edit", you can tell
git-rebase to stop after applying that commit, so that you can edit
the files and/or the commit message, amend the commit, and continue
If you want to fold two or more commits into one, replace the command "pick" with "squash" for the second and subsequent commit. If the commits had different authors, it will attribute the squashed commit to the author of the first commit.
In both cases, or when a "pick" does not succeed (because of merge
errors), the loop will stop to let you fix things, and you can continue
the loop with
git rebase --continue.
For example, if you want to reorder the last 5 commits, such that what
was HEAD~4 becomes the new HEAD. To achieve that, you would call
git-rebase like this:
$ git rebase -i HEAD~5
And move the first patch to the end of the list.
You might want to preserve merges, if you have a history like this:
X \ A---M---B / ---o---O---P---Q
Suppose you want to rebase the side branch starting at "A" to "Q". Make sure that the current HEAD is "B", and call
$ git rebase -i -p --onto Q O
In interactive mode, you can mark commits with the action "edit". However, this does not necessarily mean that git rebase expects the result of this edit to be exactly one commit. Indeed, you can undo the commit, or you can add other commits. This can be used to split a commit into two:
Start an interactive rebase with git rebase -i <commit>^, where <commit> is the commit you want to split. In fact, any commit range will do, as long as it contains that commit.
Mark the commit you want to split with the action "edit".
When it comes to editing that commit, execute git reset HEAD^. The effect is that the HEAD is rewound by one, and the index follows suit. However, the working tree stays the same.
Commit the now-current index with whatever commit message is appropriate now.
Repeat the last two steps until your working tree is clean.
Continue the rebase with git rebase --continue.
If you are not absolutely sure that the intermediate revisions are consistent (they compile, pass the testsuite, etc.) you should use git-stash to stash away the not-yet-committed changes after each commit, test, and amend the commit if fixes are necessary.
Documentation by Junio C Hamano and the git-list <email@example.com>.
Part of the git suite