1git-rebase(1) 2============= 3 4NAME 5---- 6git-rebase - Forward-port local commits to the updated upstream head 7 8SYNOPSIS 9-------- 10[verse] 11'git rebase' [-i | --interactive] [-v | --verbose] [-m | --merge] 12 [-s <strategy> | --strategy=<strategy>] [--no-verify] 13 [-C<n>] [ --whitespace=<option>] [-p | --preserve-merges] 14 [--onto <newbase>] <upstream> [<branch>] 15'git rebase' --continue | --skip | --abort 16 17DESCRIPTION 18----------- 19If <branch> is specified, 'git-rebase' will perform an automatic 20`git checkout <branch>` before doing anything else. Otherwise 21it remains on the current branch. 22 23All changes made by commits in the current branch but that are not 24in <upstream> are saved to a temporary area. This is the same set 25of commits that would be shown by `git log <upstream>..HEAD`. 26 27The current branch is reset to <upstream>, or <newbase> if the 28--onto option was supplied. This has the exact same effect as 29`git reset --hard <upstream>` (or <newbase>). ORIG_HEAD is set 30to point at the tip of the branch before the reset. 31 32The commits that were previously saved into the temporary area are 33then reapplied to the current branch, one by one, in order. Note that 34any commits in HEAD which introduce the same textual changes as a commit 35in HEAD..<upstream> are omitted (i.e., a patch already accepted upstream 36with a different commit message or timestamp will be skipped). 37 38It is possible that a merge failure will prevent this process from being 39completely automatic. You will have to resolve any such merge failure 40and run `git rebase --continue`. Another option is to bypass the commit 41that caused the merge failure with `git rebase --skip`. To restore the 42original <branch> and remove the .git/rebase-apply working files, use the 43command `git rebase --abort` instead. 44 45Assume the following history exists and the current branch is "topic": 46 47------------ 48 A---B---C topic 49 / 50 D---E---F---G master 51------------ 52 53From this point, the result of either of the following commands: 54 55 56 git rebase master 57 git rebase master topic 58 59would be: 60 61------------ 62 A'--B'--C' topic 63 / 64 D---E---F---G master 65------------ 66 67The latter form is just a short-hand of `git checkout topic` 68followed by `git rebase master`. 69 70If the upstream branch already contains a change you have made (e.g., 71because you mailed a patch which was applied upstream), then that commit 72will be skipped. For example, running `git rebase master` on the 73following history (in which A' and A introduce the same set of changes, 74but have different committer information): 75 76------------ 77 A---B---C topic 78 / 79 D---E---A'---F master 80------------ 81 82will result in: 83 84------------ 85 B'---C' topic 86 / 87 D---E---A'---F master 88------------ 89 90Here is how you would transplant a topic branch based on one 91branch to another, to pretend that you forked the topic branch 92from the latter branch, using `rebase --onto`. 93 94First let's assume your 'topic' is based on branch 'next'. 95For example, a feature developed in 'topic' depends on some 96functionality which is found in 'next'. 97 98------------ 99 o---o---o---o---o master 100 \ 101 o---o---o---o---o next 102 \ 103 o---o---o topic 104------------ 105 106We want to make 'topic' forked from branch 'master'; for example, 107because the functionality on which 'topic' depends was merged into the 108more stable 'master' branch. We want our tree to look like this: 109 110------------ 111 o---o---o---o---o master 112 | \ 113 | o'--o'--o' topic 114 \ 115 o---o---o---o---o next 116------------ 117 118We can get this using the following command: 119 120 git rebase --onto master next topic 121 122 123Another example of --onto option is to rebase part of a 124branch. If we have the following situation: 125 126------------ 127 H---I---J topicB 128 / 129 E---F---G topicA 130 / 131 A---B---C---D master 132------------ 133 134then the command 135 136 git rebase --onto master topicA topicB 137 138would result in: 139 140------------ 141 H'--I'--J' topicB 142 / 143 | E---F---G topicA 144 |/ 145 A---B---C---D master 146------------ 147 148This is useful when topicB does not depend on topicA. 149 150A range of commits could also be removed with rebase. If we have 151the following situation: 152 153------------ 154 E---F---G---H---I---J topicA 155------------ 156 157then the command 158 159 git rebase --onto topicA~5 topicA~3 topicA 160 161would result in the removal of commits F and G: 162 163------------ 164 E---H'---I'---J' topicA 165------------ 166 167This is useful if F and G were flawed in some way, or should not be 168part of topicA. Note that the argument to --onto and the <upstream> 169parameter can be any valid commit-ish. 170 171In case of conflict, 'git-rebase' will stop at the first problematic commit 172and leave conflict markers in the tree. You can use 'git-diff' to locate 173the markers (<<<<<<) and make edits to resolve the conflict. For each 174file you edit, you need to tell git that the conflict has been resolved, 175typically this would be done with 176 177 178 git add <filename> 179 180 181After resolving the conflict manually and updating the index with the 182desired resolution, you can continue the rebasing process with 183 184 185 git rebase --continue 186 187 188Alternatively, you can undo the 'git-rebase' with 189 190 191 git rebase --abort 192 193OPTIONS 194------- 195<newbase>:: 196 Starting point at which to create the new commits. If the 197 --onto option is not specified, the starting point is 198 <upstream>. May be any valid commit, and not just an 199 existing branch name. 200 201<upstream>:: 202 Upstream branch to compare against. May be any valid commit, 203 not just an existing branch name. 204 205<branch>:: 206 Working branch; defaults to HEAD. 207 208--continue:: 209 Restart the rebasing process after having resolved a merge conflict. 210 211--abort:: 212 Restore the original branch and abort the rebase operation. 213 214--skip:: 215 Restart the rebasing process by skipping the current patch. 216 217-m:: 218--merge:: 219 Use merging strategies to rebase. When the recursive (default) merge 220 strategy is used, this allows rebase to be aware of renames on the 221 upstream side. 222 223-s <strategy>:: 224--strategy=<strategy>:: 225 Use the given merge strategy; can be supplied more than 226 once to specify them in the order they should be tried. 227 If there is no `-s` option, a built-in list of strategies 228 is used instead ('git-merge-recursive' when merging a single 229 head, 'git-merge-octopus' otherwise). This implies --merge. 230 231-v:: 232--verbose:: 233 Display a diffstat of what changed upstream since the last rebase. 234 235--no-verify:: 236 This option bypasses the pre-rebase hook. See also linkgit:githooks[5]. 237 238-C<n>:: 239 Ensure at least <n> lines of surrounding context match before 240 and after each change. When fewer lines of surrounding 241 context exist they all must match. By default no context is 242 ever ignored. 243 244--whitespace=<nowarn|warn|error|error-all|strip>:: 245 This flag is passed to the 'git-apply' program 246 (see linkgit:git-apply[1]) that applies the patch. 247 248-i:: 249--interactive:: 250 Make a list of the commits which are about to be rebased. Let the 251 user edit that list before rebasing. This mode can also be used to 252 split commits (see SPLITTING COMMITS below). 253 254-p:: 255--preserve-merges:: 256 Instead of ignoring merges, try to recreate them. 257 258include::merge-strategies.txt[] 259 260NOTES 261----- 262When you rebase a branch, you are changing its history in a way that 263will cause problems for anyone who already has a copy of the branch 264in their repository and tries to pull updates from you. You should 265understand the implications of using 'git-rebase' on a repository that 266you share. 267 268When the git-rebase command is run, it will first execute a "pre-rebase" 269hook if one exists. You can use this hook to do sanity checks and 270reject the rebase if it isn't appropriate. Please see the template 271pre-rebase hook script for an example. 272 273Upon completion, <branch> will be the current branch. 274 275INTERACTIVE MODE 276---------------- 277 278Rebasing interactively means that you have a chance to edit the commits 279which are rebased. You can reorder the commits, and you can 280remove them (weeding out bad or otherwise unwanted patches). 281 282The interactive mode is meant for this type of workflow: 283 2841. have a wonderful idea 2852. hack on the code 2863. prepare a series for submission 2874. submit 288 289where point 2. consists of several instances of 290 291a. regular use 292 1. finish something worthy of a commit 293 2. commit 294b. independent fixup 295 1. realize that something does not work 296 2. fix that 297 3. commit it 298 299Sometimes the thing fixed in b.2. cannot be amended to the not-quite 300perfect commit it fixes, because that commit is buried deeply in a 301patch series. That is exactly what interactive rebase is for: use it 302after plenty of "a"s and "b"s, by rearranging and editing 303commits, and squashing multiple commits into one. 304 305Start it with the last commit you want to retain as-is: 306 307 git rebase -i <after-this-commit> 308 309An editor will be fired up with all the commits in your current branch 310(ignoring merge commits), which come after the given commit. You can 311reorder the commits in this list to your heart's content, and you can 312remove them. The list looks more or less like this: 313 314------------------------------------------- 315pick deadbee The oneline of this commit 316pick fa1afe1 The oneline of the next commit 317... 318------------------------------------------- 319 320The oneline descriptions are purely for your pleasure; 'git-rebase' will 321not look at them but at the commit names ("deadbee" and "fa1afe1" in this 322example), so do not delete or edit the names. 323 324By replacing the command "pick" with the command "edit", you can tell 325'git-rebase' to stop after applying that commit, so that you can edit 326the files and/or the commit message, amend the commit, and continue 327rebasing. 328 329If you want to fold two or more commits into one, replace the command 330"pick" with "squash" for the second and subsequent commit. If the 331commits had different authors, it will attribute the squashed commit to 332the author of the first commit. 333 334In both cases, or when a "pick" does not succeed (because of merge 335errors), the loop will stop to let you fix things, and you can continue 336the loop with `git rebase --continue`. 337 338For example, if you want to reorder the last 5 commits, such that what 339was HEAD~4 becomes the new HEAD. To achieve that, you would call 340'git-rebase' like this: 341 342---------------------- 343$ git rebase -i HEAD~5 344---------------------- 345 346And move the first patch to the end of the list. 347 348You might want to preserve merges, if you have a history like this: 349 350------------------ 351 X 352 \ 353 A---M---B 354 / 355---o---O---P---Q 356------------------ 357 358Suppose you want to rebase the side branch starting at "A" to "Q". Make 359sure that the current HEAD is "B", and call 360 361----------------------------- 362$ git rebase -i -p --onto Q O 363----------------------------- 364 365 366SPLITTING COMMITS 367----------------- 368 369In interactive mode, you can mark commits with the action "edit". However, 370this does not necessarily mean that 'git-rebase' expects the result of this 371edit to be exactly one commit. Indeed, you can undo the commit, or you can 372add other commits. This can be used to split a commit into two: 373 374- Start an interactive rebase with `git rebase -i <commit>^`, where 375 <commit> is the commit you want to split. In fact, any commit range 376 will do, as long as it contains that commit. 377 378- Mark the commit you want to split with the action "edit". 379 380- When it comes to editing that commit, execute `git reset HEAD^`. The 381 effect is that the HEAD is rewound by one, and the index follows suit. 382 However, the working tree stays the same. 383 384- Now add the changes to the index that you want to have in the first 385 commit. You can use `git add` (possibly interactively) or 386 'git-gui' (or both) to do that. 387 388- Commit the now-current index with whatever commit message is appropriate 389 now. 390 391- Repeat the last two steps until your working tree is clean. 392 393- Continue the rebase with `git rebase --continue`. 394 395If you are not absolutely sure that the intermediate revisions are 396consistent (they compile, pass the testsuite, etc.) you should use 397'git-stash' to stash away the not-yet-committed changes 398after each commit, test, and amend the commit if fixes are necessary. 399 400 401Authors 402------ 403Written by Junio C Hamano <gitster@pobox.com> and 404Johannes E. Schindelin <johannes.schindelin@gmx.de> 405 406Documentation 407-------------- 408Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>. 409 410GIT 411--- 412Part of the linkgit:git[1] suite