]>
Commit | Line | Data |
---|---|---|
215a7ad1 JH |
1 | git-rebase(1) |
2 | ============= | |
7fc9d69f JH |
3 | |
4 | NAME | |
5 | ---- | |
b385085b | 6 | git-rebase - Reapply commits on top of another base tip |
7fc9d69f JH |
7 | |
8 | SYNOPSIS | |
9 | -------- | |
e448ff87 | 10 | [verse] |
414d924b DL |
11 | 'git rebase' [-i | --interactive] [<options>] [--exec <cmd>] |
12 | [--onto <newbase> | --keep-base] [<upstream> [<branch>]] | |
de613050 | 13 | 'git rebase' [-i | --interactive] [<options>] [--exec <cmd>] [--onto <newbase>] |
be496621 | 14 | --root [<branch>] |
437591a9 | 15 | 'git rebase' (--continue | --skip | --abort | --quit | --edit-todo | --show-current-patch) |
031321c6 | 16 | |
7fc9d69f JH |
17 | DESCRIPTION |
18 | ----------- | |
0b444cdb | 19 | If <branch> is specified, 'git rebase' will perform an automatic |
328c6cb8 | 20 | `git switch <branch>` before doing anything else. Otherwise |
5ca2db53 SP |
21 | it remains on the current branch. |
22 | ||
15a147e6 | 23 | If <upstream> is not specified, the upstream configured in |
f51a48ec SO |
24 | branch.<name>.remote and branch.<name>.merge options will be used (see |
25 | linkgit:git-config[1] for details) and the `--fork-point` option is | |
26 | assumed. If you are currently not on any branch or if the current | |
27 | branch does not have a configured upstream, the rebase will abort. | |
15a147e6 | 28 | |
5ca2db53 SP |
29 | All changes made by commits in the current branch but that are not |
30 | in <upstream> are saved to a temporary area. This is the same set | |
f51a48ec SO |
31 | of commits that would be shown by `git log <upstream>..HEAD`; or by |
32 | `git log 'fork_point'..HEAD`, if `--fork-point` is active (see the | |
33 | description on `--fork-point` below); or by `git log HEAD`, if the | |
34 | `--root` option is specified. | |
5ca2db53 SP |
35 | |
36 | The current branch is reset to <upstream>, or <newbase> if the | |
37 | --onto option was supplied. This has the exact same effect as | |
9869099b BG |
38 | `git reset --hard <upstream>` (or <newbase>). ORIG_HEAD is set |
39 | to point at the tip of the branch before the reset. | |
5ca2db53 SP |
40 | |
41 | The commits that were previously saved into the temporary area are | |
ff905462 JK |
42 | then reapplied to the current branch, one by one, in order. Note that |
43 | any commits in HEAD which introduce the same textual changes as a commit | |
44 | in HEAD..<upstream> are omitted (i.e., a patch already accepted upstream | |
45 | with a different commit message or timestamp will be skipped). | |
69a60af5 | 46 | |
031321c6 SE |
47 | It is possible that a merge failure will prevent this process from being |
48 | completely automatic. You will have to resolve any such merge failure | |
cc120056 | 49 | and run `git rebase --continue`. Another option is to bypass the commit |
5960bc9d | 50 | that caused the merge failure with `git rebase --skip`. To check out the |
51ef1daa JS |
51 | original <branch> and remove the .git/rebase-apply working files, use the |
52 | command `git rebase --abort` instead. | |
031321c6 | 53 | |
69a60af5 CW |
54 | Assume the following history exists and the current branch is "topic": |
55 | ||
031321c6 | 56 | ------------ |
69a60af5 CW |
57 | A---B---C topic |
58 | / | |
59 | D---E---F---G master | |
031321c6 | 60 | ------------ |
69a60af5 | 61 | |
228382ae | 62 | From this point, the result of either of the following commands: |
69a60af5 | 63 | |
031321c6 | 64 | |
b1889c36 JN |
65 | git rebase master |
66 | git rebase master topic | |
69a60af5 CW |
67 | |
68 | would be: | |
69 | ||
031321c6 | 70 | ------------ |
69a60af5 CW |
71 | A'--B'--C' topic |
72 | / | |
73 | D---E---F---G master | |
031321c6 | 74 | ------------ |
69a60af5 | 75 | |
ee55703b DN |
76 | *NOTE:* The latter form is just a short-hand of `git checkout topic` |
77 | followed by `git rebase master`. When rebase exits `topic` will | |
78 | remain the checked-out branch. | |
69a60af5 | 79 | |
ff905462 JK |
80 | If the upstream branch already contains a change you have made (e.g., |
81 | because you mailed a patch which was applied upstream), then that commit | |
b1889c36 | 82 | will be skipped. For example, running `git rebase master` on the |
e08bc7a9 | 83 | following history (in which `A'` and `A` introduce the same set of changes, |
ff905462 JK |
84 | but have different committer information): |
85 | ||
86 | ------------ | |
87 | A---B---C topic | |
88 | / | |
89 | D---E---A'---F master | |
90 | ------------ | |
91 | ||
92 | will result in: | |
93 | ||
94 | ------------ | |
95 | B'---C' topic | |
96 | / | |
97 | D---E---A'---F master | |
98 | ------------ | |
99 | ||
e52775f4 JN |
100 | Here is how you would transplant a topic branch based on one |
101 | branch to another, to pretend that you forked the topic branch | |
102 | from the latter branch, using `rebase --onto`. | |
69a60af5 | 103 | |
e52775f4 | 104 | First let's assume your 'topic' is based on branch 'next'. |
e2b850b2 | 105 | For example, a feature developed in 'topic' depends on some |
e52775f4 | 106 | functionality which is found in 'next'. |
69a60af5 | 107 | |
031321c6 | 108 | ------------ |
e52775f4 JN |
109 | o---o---o---o---o master |
110 | \ | |
111 | o---o---o---o---o next | |
112 | \ | |
113 | o---o---o topic | |
114 | ------------ | |
115 | ||
e2b850b2 GD |
116 | We want to make 'topic' forked from branch 'master'; for example, |
117 | because the functionality on which 'topic' depends was merged into the | |
118 | more stable 'master' branch. We want our tree to look like this: | |
e52775f4 JN |
119 | |
120 | ------------ | |
121 | o---o---o---o---o master | |
122 | | \ | |
123 | | o'--o'--o' topic | |
124 | \ | |
125 | o---o---o---o---o next | |
031321c6 | 126 | ------------ |
7fc9d69f | 127 | |
e52775f4 JN |
128 | We can get this using the following command: |
129 | ||
b1889c36 | 130 | git rebase --onto master next topic |
e52775f4 JN |
131 | |
132 | ||
133 | Another example of --onto option is to rebase part of a | |
134 | branch. If we have the following situation: | |
135 | ||
136 | ------------ | |
137 | H---I---J topicB | |
138 | / | |
139 | E---F---G topicA | |
140 | / | |
141 | A---B---C---D master | |
142 | ------------ | |
143 | ||
144 | then the command | |
145 | ||
b1889c36 | 146 | git rebase --onto master topicA topicB |
e52775f4 JN |
147 | |
148 | would result in: | |
149 | ||
150 | ------------ | |
151 | H'--I'--J' topicB | |
152 | / | |
153 | | E---F---G topicA | |
154 | |/ | |
155 | A---B---C---D master | |
156 | ------------ | |
157 | ||
158 | This is useful when topicB does not depend on topicA. | |
159 | ||
ea81fcc5 SP |
160 | A range of commits could also be removed with rebase. If we have |
161 | the following situation: | |
162 | ||
163 | ------------ | |
164 | E---F---G---H---I---J topicA | |
165 | ------------ | |
166 | ||
167 | then the command | |
168 | ||
b1889c36 | 169 | git rebase --onto topicA~5 topicA~3 topicA |
ea81fcc5 SP |
170 | |
171 | would result in the removal of commits F and G: | |
172 | ||
173 | ------------ | |
174 | E---H'---I'---J' topicA | |
175 | ------------ | |
176 | ||
177 | This is useful if F and G were flawed in some way, or should not be | |
178 | part of topicA. Note that the argument to --onto and the <upstream> | |
179 | parameter can be any valid commit-ish. | |
180 | ||
0b444cdb TR |
181 | In case of conflict, 'git rebase' will stop at the first problematic commit |
182 | and leave conflict markers in the tree. You can use 'git diff' to locate | |
031321c6 | 183 | the markers (<<<<<<) and make edits to resolve the conflict. For each |
2de9b711 | 184 | file you edit, you need to tell Git that the conflict has been resolved, |
031321c6 SE |
185 | typically this would be done with |
186 | ||
187 | ||
d7f078b8 | 188 | git add <filename> |
031321c6 SE |
189 | |
190 | ||
191 | After resolving the conflict manually and updating the index with the | |
192 | desired resolution, you can continue the rebasing process with | |
193 | ||
194 | ||
195 | git rebase --continue | |
8978d043 | 196 | |
8978d043 | 197 | |
0b444cdb | 198 | Alternatively, you can undo the 'git rebase' with |
8978d043 | 199 | |
031321c6 SE |
200 | |
201 | git rebase --abort | |
8978d043 | 202 | |
7fc9d69f JH |
203 | OPTIONS |
204 | ------- | |
c2145384 | 205 | --onto <newbase>:: |
69a60af5 CW |
206 | Starting point at which to create the new commits. If the |
207 | --onto option is not specified, the starting point is | |
ea81fcc5 SP |
208 | <upstream>. May be any valid commit, and not just an |
209 | existing branch name. | |
873c3472 | 210 | + |
b9190e79 | 211 | As a special case, you may use "A\...B" as a shortcut for the |
873c3472 MG |
212 | merge base of A and B if there is exactly one merge base. You can |
213 | leave out at most one of A and B, in which case it defaults to HEAD. | |
69a60af5 | 214 | |
414d924b DL |
215 | --keep-base:: |
216 | Set the starting point at which to create the new commits to the | |
217 | merge base of <upstream> <branch>. Running | |
218 | 'git rebase --keep-base <upstream> <branch>' is equivalent to | |
219 | running 'git rebase --onto <upstream>... <upstream>'. | |
220 | + | |
221 | This option is useful in the case where one is developing a feature on | |
222 | top of an upstream branch. While the feature is being worked on, the | |
223 | upstream branch may advance and it may not be the best idea to keep | |
224 | rebasing on top of the upstream but to keep the base commit as-is. | |
225 | + | |
226 | Although both this option and --fork-point find the merge base between | |
227 | <upstream> and <branch>, this option uses the merge base as the _starting | |
228 | point_ on which new commits will be created, whereas --fork-point uses | |
229 | the merge base to determine the _set of commits_ which will be rebased. | |
230 | + | |
231 | See also INCOMPATIBLE OPTIONS below. | |
232 | ||
52a22d1e | 233 | <upstream>:: |
ea81fcc5 | 234 | Upstream branch to compare against. May be any valid commit, |
15a147e6 MZ |
235 | not just an existing branch name. Defaults to the configured |
236 | upstream for the current branch. | |
7fc9d69f | 237 | |
228382ae | 238 | <branch>:: |
52a22d1e | 239 | Working branch; defaults to HEAD. |
7fc9d69f | 240 | |
031321c6 SE |
241 | --continue:: |
242 | Restart the rebasing process after having resolved a merge conflict. | |
243 | ||
244 | --abort:: | |
5960bc9d MZ |
245 | Abort the rebase operation and reset HEAD to the original |
246 | branch. If <branch> was provided when the rebase operation was | |
247 | started, then HEAD will be reset to <branch>. Otherwise HEAD | |
248 | will be reset to where it was when the rebase operation was | |
249 | started. | |
031321c6 | 250 | |
9512177b NTND |
251 | --quit:: |
252 | Abort the rebase operation but HEAD is not reset back to the | |
253 | original branch. The index and working tree are also left | |
9b2df3e8 | 254 | unchanged as a result. If a temporary stash entry was created |
c5e786ab | 255 | using --autostash, it will be saved to the stash list. |
9512177b | 256 | |
81de0c01 | 257 | --apply:: |
10cdb9f3 EN |
258 | Use applying strategies to rebase (calling `git-am` |
259 | internally). This option may become a no-op in the future | |
260 | once the merge backend handles everything the apply one does. | |
52eb738d EN |
261 | + |
262 | See also INCOMPATIBLE OPTIONS below. | |
263 | ||
e98c4269 EN |
264 | --empty={drop,keep,ask}:: |
265 | How to handle commits that are not empty to start and are not | |
266 | clean cherry-picks of any upstream commit, but which become | |
267 | empty after rebasing (because they contain a subset of already | |
268 | upstream changes). With drop (the default), commits that | |
269 | become empty are dropped. With keep, such commits are kept. | |
270 | With ask (implied by --interactive), the rebase will halt when | |
271 | an empty commit is applied allowing you to choose whether to | |
272 | drop it, edit files more, or just commit the empty changes. | |
273 | Other options, like --exec, will use the default of drop unless | |
274 | -i/--interactive is explicitly specified. | |
275 | + | |
b9cbd295 EN |
276 | Note that commits which start empty are kept (unless --no-keep-empty |
277 | is specified), and commits which are clean cherry-picks (as determined | |
0fcb4f6b JT |
278 | by `git log --cherry-mark ...`) are detected and dropped as a |
279 | preliminary step (unless --reapply-cherry-picks is passed). | |
e98c4269 EN |
280 | + |
281 | See also INCOMPATIBLE OPTIONS below. | |
282 | ||
b9cbd295 | 283 | --no-keep-empty:: |
90e1818f | 284 | --keep-empty:: |
b9cbd295 EN |
285 | Do not keep commits that start empty before the rebase |
286 | (i.e. that do not change anything from its parent) in the | |
287 | result. The default is to keep commits which start empty, | |
288 | since creating such commits requires passing the --allow-empty | |
289 | override flag to `git commit`, signifying that a user is very | |
290 | intentionally creating such a commit and thus wants to keep | |
291 | it. | |
292 | + | |
293 | Usage of this flag will probably be rare, since you can get rid of | |
294 | commits that start empty by just firing up an interactive rebase and | |
295 | removing the lines corresponding to the commits you don't want. This | |
296 | flag exists as a convenient shortcut, such as for cases where external | |
297 | tools generate many empty commits and you want them all removed. | |
298 | + | |
299 | For commits which do not start empty but become empty after rebasing, | |
300 | see the --empty flag. | |
5dacd4ab | 301 | + |
b9cbd295 | 302 | See also INCOMPATIBLE OPTIONS below. |
90e1818f | 303 | |
0fcb4f6b JT |
304 | --reapply-cherry-picks:: |
305 | --no-reapply-cherry-picks:: | |
306 | Reapply all clean cherry-picks of any upstream commit instead | |
307 | of preemptively dropping them. (If these commits then become | |
308 | empty after rebasing, because they contain a subset of already | |
309 | upstream changes, the behavior towards them is controlled by | |
310 | the `--empty` flag.) | |
311 | + | |
312 | By default (or if `--no-reapply-cherry-picks` is given), these commits | |
313 | will be automatically dropped. Because this necessitates reading all | |
314 | upstream commits, this can be expensive in repos with a large number | |
315 | of upstream commits that need to be read. | |
316 | + | |
317 | `--reapply-cherry-picks` allows rebase to forgo reading all upstream | |
318 | commits, potentially improving performance. | |
319 | + | |
320 | See also INCOMPATIBLE OPTIONS below. | |
321 | ||
a6c612b5 | 322 | --allow-empty-message:: |
22a69fda EN |
323 | No-op. Rebasing commits with an empty message used to fail |
324 | and this option would override that behavior, allowing commits | |
325 | with empty messages to be rebased. Now commits with an empty | |
326 | message do not cause rebasing to halt. | |
5dacd4ab EN |
327 | + |
328 | See also INCOMPATIBLE OPTIONS below. | |
a6c612b5 | 329 | |
58634dbf EW |
330 | --skip:: |
331 | Restart the rebasing process by skipping the current patch. | |
58634dbf | 332 | |
eb9a7cb4 AW |
333 | --edit-todo:: |
334 | Edit the todo list during an interactive rebase. | |
335 | ||
66335298 NTND |
336 | --show-current-patch:: |
337 | Show the current patch in an interactive rebase or when rebase | |
fbd7a232 NTND |
338 | is stopped because of conflicts. This is the equivalent of |
339 | `git show REBASE_HEAD`. | |
66335298 | 340 | |
3240240f SB |
341 | -m:: |
342 | --merge:: | |
58634dbf EW |
343 | Use merging strategies to rebase. When the recursive (default) merge |
344 | strategy is used, this allows rebase to be aware of renames on the | |
2ac0d627 | 345 | upstream side. This is the default. |
31ddd1ee TR |
346 | + |
347 | Note that a rebase merge works by replaying each commit from the working | |
348 | branch on top of the <upstream> branch. Because of this, when a merge | |
349 | conflict happens, the side reported as 'ours' is the so-far rebased | |
350 | series, starting with <upstream>, and 'theirs' is the working branch. In | |
351 | other words, the sides are swapped. | |
5dacd4ab EN |
352 | + |
353 | See also INCOMPATIBLE OPTIONS below. | |
58634dbf | 354 | |
3240240f SB |
355 | -s <strategy>:: |
356 | --strategy=<strategy>:: | |
06f39190 | 357 | Use the given merge strategy. |
0b444cdb | 358 | If there is no `-s` option 'git merge-recursive' is used |
31ddd1ee TR |
359 | instead. This implies --merge. |
360 | + | |
0b444cdb | 361 | Because 'git rebase' replays each commit from the working branch |
31ddd1ee | 362 | on top of the <upstream> branch using the given strategy, using |
5dacd4ab | 363 | the 'ours' strategy simply empties all patches from the <branch>, |
31ddd1ee | 364 | which makes little sense. |
5dacd4ab EN |
365 | + |
366 | See also INCOMPATIBLE OPTIONS below. | |
58634dbf | 367 | |
93ce190c ML |
368 | -X <strategy-option>:: |
369 | --strategy-option=<strategy-option>:: | |
370 | Pass the <strategy-option> through to the merge strategy. | |
6cf378f0 | 371 | This implies `--merge` and, if no strategy has been |
93ce190c | 372 | specified, `-s recursive`. Note the reversal of 'ours' and |
edfbbf7e | 373 | 'theirs' as noted above for the `-m` option. |
5dacd4ab EN |
374 | + |
375 | See also INCOMPATIBLE OPTIONS below. | |
93ce190c | 376 | |
aba4954c PW |
377 | --rerere-autoupdate:: |
378 | --no-rerere-autoupdate:: | |
379 | Allow the rerere mechanism to update the index with the | |
380 | result of auto-conflict resolution if possible. | |
381 | ||
3ee5e540 NV |
382 | -S[<keyid>]:: |
383 | --gpg-sign[=<keyid>]:: | |
c241371c | 384 | --no-gpg-sign:: |
2b594bf9 MM |
385 | GPG-sign commits. The `keyid` argument is optional and |
386 | defaults to the committer identity; if specified, it must be | |
c241371c ĐTCD |
387 | stuck to the option without a space. `--no-gpg-sign` is useful to |
388 | countermand both `commit.gpgSign` configuration variable, and | |
389 | earlier `--gpg-sign`. | |
3ee5e540 | 390 | |
0e987a12 SB |
391 | -q:: |
392 | --quiet:: | |
393 | Be quiet. Implies --no-stat. | |
394 | ||
3240240f SB |
395 | -v:: |
396 | --verbose:: | |
a9c3821c TAV |
397 | Be verbose. Implies --stat. |
398 | ||
399 | --stat:: | |
400 | Show a diffstat of what changed upstream since the last rebase. The | |
401 | diffstat is also controlled by the configuration option rebase.stat. | |
402 | ||
403 | -n:: | |
404 | --no-stat:: | |
405 | Do not show a diffstat as part of the rebase process. | |
b758789c | 406 | |
fd631d58 NS |
407 | --no-verify:: |
408 | This option bypasses the pre-rebase hook. See also linkgit:githooks[5]. | |
409 | ||
7baf9c4b MZ |
410 | --verify:: |
411 | Allows the pre-rebase hook to run, which is the default. This option can | |
412 | be used to override --no-verify. See also linkgit:githooks[5]. | |
413 | ||
67dad687 MT |
414 | -C<n>:: |
415 | Ensure at least <n> lines of surrounding context match before | |
416 | and after each change. When fewer lines of surrounding | |
417 | context exist they all must match. By default no context is | |
10cdb9f3 | 418 | ever ignored. Implies --apply. |
5dacd4ab EN |
419 | + |
420 | See also INCOMPATIBLE OPTIONS below. | |
67dad687 | 421 | |
983f464f | 422 | --no-ff:: |
5e75d56f | 423 | --force-rebase:: |
983f464f EN |
424 | -f:: |
425 | Individually replay all rebased commits instead of fast-forwarding | |
426 | over the unchanged ones. This ensures that the entire history of | |
427 | the rebased branch is composed of new commits. | |
b4995494 | 428 | + |
983f464f EN |
429 | You may find this helpful after reverting a topic branch merge, as this option |
430 | recreates the topic branch with fresh commits so it can be remerged | |
431 | successfully without needing to "revert the reversion" (see the | |
432 | link:howto/revert-a-faulty-merge.html[revert-a-faulty-merge How-To] for | |
433 | details). | |
5e75d56f | 434 | |
ad8261d2 JK |
435 | --fork-point:: |
436 | --no-fork-point:: | |
f51a48ec SO |
437 | Use reflog to find a better common ancestor between <upstream> |
438 | and <branch> when calculating which commits have been | |
439 | introduced by <branch>. | |
ad8261d2 | 440 | + |
f51a48ec SO |
441 | When --fork-point is active, 'fork_point' will be used instead of |
442 | <upstream> to calculate the set of commits to rebase, where | |
443 | 'fork_point' is the result of `git merge-base --fork-point <upstream> | |
444 | <branch>` command (see linkgit:git-merge-base[1]). If 'fork_point' | |
445 | ends up being empty, the <upstream> will be used as a fallback. | |
446 | + | |
a35413c3 EN |
447 | If <upstream> is given on the command line, then the default is |
448 | `--no-fork-point`, otherwise the default is `--fork-point`. | |
414d924b DL |
449 | + |
450 | If your branch was based on <upstream> but <upstream> was rewound and | |
451 | your branch contains commits which were dropped, this option can be used | |
452 | with `--keep-base` in order to drop those commits from your branch. | |
a35413c3 EN |
453 | + |
454 | See also INCOMPATIBLE OPTIONS below. | |
ad8261d2 | 455 | |
86c91f91 | 456 | --ignore-whitespace:: |
ef484add RA |
457 | Ignore whitespace differences when trying to reconcile |
458 | differences. Currently, each backend implements an approximation of | |
459 | this behavior: | |
460 | + | |
461 | apply backend: When applying a patch, ignore changes in whitespace in | |
462 | context lines. Unfortunately, this means that if the "old" lines being | |
463 | replaced by the patch differ only in whitespace from the existing | |
464 | file, you will get a merge conflict instead of a successful patch | |
465 | application. | |
466 | + | |
467 | merge backend: Treat lines with only whitespace changes as unchanged | |
468 | when merging. Unfortunately, this means that any patch hunks that were | |
469 | intended to modify whitespace and nothing else will be dropped, even | |
470 | if the other side had no changes that conflicted. | |
471 | ||
749485f6 | 472 | --whitespace=<option>:: |
ef484add | 473 | This flag is passed to the 'git apply' program |
5162e697 | 474 | (see linkgit:git-apply[1]) that applies the patch. |
10cdb9f3 | 475 | Implies --apply. |
5dacd4ab EN |
476 | + |
477 | See also INCOMPATIBLE OPTIONS below. | |
059f446d | 478 | |
570ccad3 | 479 | --committer-date-is-author-date:: |
7573cec5 PW |
480 | Instead of using the current time as the committer date, use |
481 | the author date of the commit being rebased as the committer | |
482 | date. This option implies `--force-rebase`. | |
483 | ||
570ccad3 | 484 | --ignore-date:: |
27126692 | 485 | --reset-author-date:: |
a3894aad PW |
486 | Instead of using the author date of the original commit, use |
487 | the current time as the author date of the rebased commit. This | |
488 | option implies `--force-rebase`. | |
5dacd4ab EN |
489 | + |
490 | See also INCOMPATIBLE OPTIONS below. | |
570ccad3 | 491 | |
9f79524a | 492 | --signoff:: |
3abd4a67 | 493 | Add a `Signed-off-by` trailer to all the rebased commits. Note |
a852ec7f | 494 | that if `--interactive` is given then only commits marked to be |
5dacd4ab EN |
495 | picked, edited or reworded will have the trailer added. |
496 | + | |
497 | See also INCOMPATIBLE OPTIONS below. | |
9f79524a | 498 | |
3240240f SB |
499 | -i:: |
500 | --interactive:: | |
1b1dce4b | 501 | Make a list of the commits which are about to be rebased. Let the |
f0fd889d JS |
502 | user edit that list before rebasing. This mode can also be used to |
503 | split commits (see SPLITTING COMMITS below). | |
16cf51c7 MR |
504 | + |
505 | The commit list format can be changed by setting the configuration option | |
506 | rebase.instructionFormat. A customized instruction format will automatically | |
507 | have the long commit hash prepended to the format. | |
5dacd4ab EN |
508 | + |
509 | See also INCOMPATIBLE OPTIONS below. | |
1b1dce4b | 510 | |
8f6aed71 | 511 | -r:: |
7543f6f4 | 512 | --rebase-merges[=(rebase-cousins|no-rebase-cousins)]:: |
8f6aed71 JS |
513 | By default, a rebase will simply drop merge commits from the todo |
514 | list, and put the rebased commits into a single, linear branch. | |
515 | With `--rebase-merges`, the rebase will instead try to preserve | |
516 | the branching structure within the commits that are to be rebased, | |
517 | by recreating the merge commits. Any resolved merge conflicts or | |
518 | manual amendments in these merge commits will have to be | |
519 | resolved/re-applied manually. | |
520 | + | |
7543f6f4 JS |
521 | By default, or when `no-rebase-cousins` was specified, commits which do not |
522 | have `<upstream>` as direct ancestor will keep their original branch point, | |
dbf47215 | 523 | i.e. commits that would be excluded by linkgit:git-log[1]'s |
7543f6f4 JS |
524 | `--ancestry-path` option will keep their original ancestry by default. If |
525 | the `rebase-cousins` mode is turned on, such commits are instead rebased | |
526 | onto `<upstream>` (or `<onto>`, if specified). | |
527 | + | |
427c3bd2 | 528 | The `--rebase-merges` mode is similar in spirit to the deprecated |
d3a8caeb NN |
529 | `--preserve-merges` but works with interactive rebases, |
530 | where commits can be reordered, inserted and dropped at will. | |
8f6aed71 JS |
531 | + |
532 | It is currently only possible to recreate the merge commits using the | |
533 | `recursive` merge strategy; Different merge strategies can be used only via | |
534 | explicit `exec git merge -s <strategy> [...]` commands. | |
25cff9f1 | 535 | + |
5dacd4ab | 536 | See also REBASING MERGES and INCOMPATIBLE OPTIONS below. |
8f6aed71 | 537 | |
3240240f SB |
538 | -p:: |
539 | --preserve-merges:: | |
427c3bd2 JS |
540 | [DEPRECATED: use `--rebase-merges` instead] Recreate merge commits |
541 | instead of flattening the history by replaying commits a merge commit | |
542 | introduces. Merge conflict resolutions or manual amendments to merge | |
543 | commits are not preserved. | |
cddb42d2 JN |
544 | + |
545 | This uses the `--interactive` machinery internally, but combining it | |
546 | with the `--interactive` option explicitly is generally not a good | |
547 | idea unless you know what you are doing (see BUGS below). | |
5dacd4ab EN |
548 | + |
549 | See also INCOMPATIBLE OPTIONS below. | |
cddb42d2 | 550 | |
c2145384 LK |
551 | -x <cmd>:: |
552 | --exec <cmd>:: | |
553 | Append "exec <cmd>" after each line creating a commit in the | |
554 | final history. <cmd> will be interpreted as one or more shell | |
b8c0b210 JS |
555 | commands. Any command that fails will interrupt the rebase, |
556 | with exit code 1. | |
c2145384 | 557 | + |
c2145384 LK |
558 | You may execute several commands by either using one instance of `--exec` |
559 | with several commands: | |
560 | + | |
561 | git rebase -i --exec "cmd1 && cmd2 && ..." | |
562 | + | |
563 | or by giving more than one `--exec`: | |
564 | + | |
565 | git rebase -i --exec "cmd1" --exec "cmd2" --exec ... | |
566 | + | |
567 | If `--autosquash` is used, "exec" lines will not be appended for | |
568 | the intermediate commits, and will only appear at the end of each | |
569 | squash/fixup series. | |
78ec2400 SB |
570 | + |
571 | This uses the `--interactive` machinery internally, but it can be run | |
572 | without an explicit `--interactive`. | |
5dacd4ab EN |
573 | + |
574 | See also INCOMPATIBLE OPTIONS below. | |
f09c9b8c | 575 | |
be496621 TR |
576 | --root:: |
577 | Rebase all commits reachable from <branch>, instead of | |
578 | limiting them with an <upstream>. This allows you to rebase | |
df5df20c | 579 | the root commit(s) on a branch. When used with --onto, it |
be496621 | 580 | will skip changes already contained in <newbase> (instead of |
df5df20c CW |
581 | <upstream>) whereas without --onto it will operate on every change. |
582 | When used together with both --onto and --preserve-merges, | |
583 | 'all' root commits will be rewritten to have <newbase> as parent | |
be496621 | 584 | instead. |
5dacd4ab EN |
585 | + |
586 | See also INCOMPATIBLE OPTIONS below. | |
be496621 | 587 | |
f59baa50 | 588 | --autosquash:: |
dd1e5b31 | 589 | --no-autosquash:: |
00ea64ed CM |
590 | When the commit log message begins with "squash! ..." or "fixup! ..." |
591 | or "amend! ...", and there is already a commit in the todo list that | |
592 | matches the same `...`, automatically modify the todo list of | |
593 | `rebase -i`, so that the commit marked for squashing comes right after | |
594 | the commit to be modified, and change the action of the moved commit | |
595 | from `pick` to `squash` or `fixup` or `fixup -C` respectively. A commit | |
596 | matches the `...` if the commit subject matches, or if the `...` refers | |
597 | to the commit's hash. As a fall-back, partial matches of the commit | |
598 | subject work, too. The recommended way to create fixup/amend/squash | |
599 | commits is by using the `--fixup`, `--fixup=amend:` or `--fixup=reword:` | |
600 | and `--squash` options respectively of linkgit:git-commit[1]. | |
f59baa50 | 601 | + |
bcf9626a | 602 | If the `--autosquash` option is enabled by default using the |
da0005b8 | 603 | configuration variable `rebase.autoSquash`, this option can be |
dd1e5b31 | 604 | used to override and disable this setting. |
5dacd4ab EN |
605 | + |
606 | See also INCOMPATIBLE OPTIONS below. | |
b4995494 | 607 | |
82e0668c JK |
608 | --autostash:: |
609 | --no-autostash:: | |
e01db917 | 610 | Automatically create a temporary stash entry before the operation |
58794775 RR |
611 | begins, and apply it after the operation ends. This means |
612 | that you can run rebase on a dirty worktree. However, use | |
613 | with care: the final stash application after a successful | |
614 | rebase might result in non-trivial conflicts. | |
615 | ||
d421afa0 JS |
616 | --reschedule-failed-exec:: |
617 | --no-reschedule-failed-exec:: | |
618 | Automatically reschedule `exec` commands that failed. This only makes | |
619 | sense in interactive mode (or when an `--exec` option was provided). | |
e5b32bff ÆAB |
620 | + |
621 | Even though this option applies once a rebase is started, it's set for | |
622 | the whole rebase at the start based on either the | |
623 | `rebase.rescheduleFailedExec` configuration (see linkgit:git-config[1] | |
624 | or "CONFIGURATION" below) or whether this option is | |
625 | provided. Otherwise an explicit `--no-reschedule-failed-exec` at the | |
626 | start would be overridden by the presence of | |
627 | `rebase.rescheduleFailedExec=true` configuration. | |
d421afa0 | 628 | |
5dacd4ab EN |
629 | INCOMPATIBLE OPTIONS |
630 | -------------------- | |
631 | ||
68aa495b | 632 | The following options: |
5dacd4ab | 633 | |
10cdb9f3 | 634 | * --apply |
be50c938 | 635 | * --whitespace |
5dacd4ab EN |
636 | * -C |
637 | ||
68aa495b | 638 | are incompatible with the following options: |
5dacd4ab EN |
639 | |
640 | * --merge | |
641 | * --strategy | |
642 | * --strategy-option | |
643 | * --allow-empty-message | |
5dacd4ab EN |
644 | * --[no-]autosquash |
645 | * --rebase-merges | |
646 | * --preserve-merges | |
647 | * --interactive | |
648 | * --exec | |
b9cbd295 | 649 | * --no-keep-empty |
e98c4269 | 650 | * --empty= |
0fcb4f6b | 651 | * --reapply-cherry-picks |
5dacd4ab EN |
652 | * --edit-todo |
653 | * --root when used in combination with --onto | |
654 | ||
68aa495b | 655 | In addition, the following pairs of options are incompatible: |
5dacd4ab EN |
656 | |
657 | * --preserve-merges and --interactive | |
658 | * --preserve-merges and --signoff | |
659 | * --preserve-merges and --rebase-merges | |
e98c4269 | 660 | * --preserve-merges and --empty= |
ef484add | 661 | * --preserve-merges and --ignore-whitespace |
7573cec5 | 662 | * --preserve-merges and --committer-date-is-author-date |
a3894aad | 663 | * --preserve-merges and --ignore-date |
414d924b DL |
664 | * --keep-base and --onto |
665 | * --keep-base and --root | |
a35413c3 | 666 | * --fork-point and --root |
5dacd4ab | 667 | |
0661e49a EN |
668 | BEHAVIORAL DIFFERENCES |
669 | ----------------------- | |
670 | ||
10cdb9f3 | 671 | git rebase has two primary backends: apply and merge. (The apply |
344420bf | 672 | backend used to be known as the 'am' backend, but the name led to |
10cdb9f3 EN |
673 | confusion as it looks like a verb instead of a noun. Also, the merge |
674 | backend used to be known as the interactive backend, but it is now | |
675 | used for non-interactive cases as well. Both were renamed based on | |
676 | lower-level functionality that underpinned each.) There are some | |
677 | subtle differences in how these two backends behave: | |
0661e49a | 678 | |
6fcbad87 JS |
679 | Empty commits |
680 | ~~~~~~~~~~~~~ | |
0661e49a | 681 | |
10cdb9f3 | 682 | The apply backend unfortunately drops intentionally empty commits, i.e. |
d48e5e21 EN |
683 | commits that started empty, though these are rare in practice. It |
684 | also drops commits that become empty and has no option for controlling | |
685 | this behavior. | |
0661e49a | 686 | |
b9cbd295 EN |
687 | The merge backend keeps intentionally empty commits by default (though |
688 | with -i they are marked as empty in the todo list editor, or they can | |
689 | be dropped automatically with --no-keep-empty). | |
690 | ||
691 | Similar to the apply backend, by default the merge backend drops | |
692 | commits that become empty unless -i/--interactive is specified (in | |
693 | which case it stops and asks the user what to do). The merge backend | |
694 | also has an --empty={drop,keep,ask} option for changing the behavior | |
695 | of handling commits that become empty. | |
0661e49a | 696 | |
6fcbad87 JS |
697 | Directory rename detection |
698 | ~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
699 | ||
be50c938 EN |
700 | Due to the lack of accurate tree information (arising from |
701 | constructing fake ancestors with the limited information available in | |
10cdb9f3 | 702 | patches), directory rename detection is disabled in the apply backend. |
be50c938 EN |
703 | Disabled directory rename detection means that if one side of history |
704 | renames a directory and the other adds new files to the old directory, | |
705 | then the new files will be left behind in the old directory without | |
706 | any warning at the time of rebasing that you may want to move these | |
707 | files into the new directory. | |
708 | ||
10cdb9f3 EN |
709 | Directory rename detection works with the merge backend to provide you |
710 | warnings in such cases. | |
be50c938 EN |
711 | |
712 | Context | |
713 | ~~~~~~~ | |
714 | ||
10cdb9f3 | 715 | The apply backend works by creating a sequence of patches (by calling |
be50c938 EN |
716 | `format-patch` internally), and then applying the patches in sequence |
717 | (calling `am` internally). Patches are composed of multiple hunks, | |
718 | each with line numbers, a context region, and the actual changes. The | |
719 | line numbers have to be taken with some fuzz, since the other side | |
720 | will likely have inserted or deleted lines earlier in the file. The | |
721 | context region is meant to help find how to adjust the line numbers in | |
722 | order to apply the changes to the right lines. However, if multiple | |
723 | areas of the code have the same surrounding lines of context, the | |
724 | wrong one can be picked. There are real-world cases where this has | |
725 | caused commits to be reapplied incorrectly with no conflicts reported. | |
726 | Setting diff.context to a larger value may prevent such types of | |
727 | problems, but increases the chance of spurious conflicts (since it | |
728 | will require more lines of matching context to apply). | |
729 | ||
10cdb9f3 | 730 | The merge backend works with a full copy of each relevant file, |
be50c938 EN |
731 | insulating it from these types of problems. |
732 | ||
733 | Labelling of conflicts markers | |
734 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
735 | ||
736 | When there are content conflicts, the merge machinery tries to | |
737 | annotate each side's conflict markers with the commits where the | |
10cdb9f3 | 738 | content came from. Since the apply backend drops the original |
be50c938 EN |
739 | information about the rebased commits and their parents (and instead |
740 | generates new fake commits based off limited information in the | |
741 | generated patches), those commits cannot be identified; instead it has | |
742 | to fall back to a commit summary. Also, when merge.conflictStyle is | |
10cdb9f3 | 743 | set to diff3, the apply backend will use "constructed merge base" to |
be50c938 EN |
744 | label the content from the merge base, and thus provide no information |
745 | about the merge base commit whatsoever. | |
746 | ||
10cdb9f3 EN |
747 | The merge backend works with the full commits on both sides of history |
748 | and thus has no such limitations. | |
be50c938 EN |
749 | |
750 | Hooks | |
751 | ~~~~~ | |
752 | ||
10cdb9f3 | 753 | The apply backend has not traditionally called the post-commit hook, |
f7139e7c EN |
754 | while the merge backend has. Both have called the post-checkout hook, |
755 | though the merge backend has squelched its output. Further, both | |
756 | backends only call the post-checkout hook with the starting point | |
757 | commit of the rebase, not the intermediate commits nor the final | |
758 | commit. In each case, the calling of these hooks was by accident of | |
759 | implementation rather than by design (both backends were originally | |
760 | implemented as shell scripts and happened to invoke other commands | |
761 | like 'git checkout' or 'git commit' that would call the hooks). Both | |
762 | backends should have the same behavior, though it is not entirely | |
763 | clear which, if any, is correct. We will likely make rebase stop | |
764 | calling either of these hooks in the future. | |
be50c938 | 765 | |
2ac0d627 EN |
766 | Interruptability |
767 | ~~~~~~~~~~~~~~~~ | |
768 | ||
10cdb9f3 EN |
769 | The apply backend has safety problems with an ill-timed interrupt; if |
770 | the user presses Ctrl-C at the wrong time to try to abort the rebase, | |
771 | the rebase can enter a state where it cannot be aborted with a | |
772 | subsequent `git rebase --abort`. The merge backend does not appear to | |
2ac0d627 EN |
773 | suffer from the same shortcoming. (See |
774 | https://lore.kernel.org/git/20200207132152.GC2868@szeder.dev/ for | |
775 | details.) | |
776 | ||
120b1eb7 EN |
777 | Commit Rewording |
778 | ~~~~~~~~~~~~~~~~ | |
779 | ||
780 | When a conflict occurs while rebasing, rebase stops and asks the user | |
781 | to resolve. Since the user may need to make notable changes while | |
782 | resolving conflicts, after conflicts are resolved and the user has run | |
783 | `git rebase --continue`, the rebase should open an editor and ask the | |
784 | user to update the commit message. The merge backend does this, while | |
785 | the apply backend blindly applies the original commit message. | |
786 | ||
be50c938 EN |
787 | Miscellaneous differences |
788 | ~~~~~~~~~~~~~~~~~~~~~~~~~ | |
789 | ||
790 | There are a few more behavioral differences that most folks would | |
791 | probably consider inconsequential but which are mentioned for | |
792 | completeness: | |
793 | ||
794 | * Reflog: The two backends will use different wording when describing | |
795 | the changes made in the reflog, though both will make use of the | |
796 | word "rebase". | |
797 | ||
798 | * Progress, informational, and error messages: The two backends | |
799 | provide slightly different progress and informational messages. | |
10cdb9f3 EN |
800 | Also, the apply backend writes error messages (such as "Your files |
801 | would be overwritten...") to stdout, while the merge backend writes | |
802 | them to stderr. | |
be50c938 EN |
803 | |
804 | * State directories: The two backends keep their state in different | |
805 | directories under .git/ | |
f59baa50 | 806 | |
58634dbf EW |
807 | include::merge-strategies.txt[] |
808 | ||
031321c6 SE |
809 | NOTES |
810 | ----- | |
90d1c08e | 811 | |
0b444cdb | 812 | You should understand the implications of using 'git rebase' on a |
90d1c08e TR |
813 | repository that you share. See also RECOVERING FROM UPSTREAM REBASE |
814 | below. | |
031321c6 | 815 | |
467c0197 | 816 | When the git-rebase command is run, it will first execute a "pre-rebase" |
031321c6 SE |
817 | hook if one exists. You can use this hook to do sanity checks and |
818 | reject the rebase if it isn't appropriate. Please see the template | |
819 | pre-rebase hook script for an example. | |
820 | ||
702088af | 821 | Upon completion, <branch> will be the current branch. |
031321c6 | 822 | |
1b1dce4b JS |
823 | INTERACTIVE MODE |
824 | ---------------- | |
825 | ||
826 | Rebasing interactively means that you have a chance to edit the commits | |
827 | which are rebased. You can reorder the commits, and you can | |
828 | remove them (weeding out bad or otherwise unwanted patches). | |
829 | ||
830 | The interactive mode is meant for this type of workflow: | |
831 | ||
832 | 1. have a wonderful idea | |
833 | 2. hack on the code | |
834 | 3. prepare a series for submission | |
835 | 4. submit | |
836 | ||
837 | where point 2. consists of several instances of | |
838 | ||
d3f2475c NBL |
839 | a) regular use |
840 | ||
1b1dce4b JS |
841 | 1. finish something worthy of a commit |
842 | 2. commit | |
d3f2475c NBL |
843 | |
844 | b) independent fixup | |
845 | ||
1b1dce4b JS |
846 | 1. realize that something does not work |
847 | 2. fix that | |
848 | 3. commit it | |
849 | ||
850 | Sometimes the thing fixed in b.2. cannot be amended to the not-quite | |
851 | perfect commit it fixes, because that commit is buried deeply in a | |
852 | patch series. That is exactly what interactive rebase is for: use it | |
853 | after plenty of "a"s and "b"s, by rearranging and editing | |
854 | commits, and squashing multiple commits into one. | |
855 | ||
856 | Start it with the last commit you want to retain as-is: | |
857 | ||
858 | git rebase -i <after-this-commit> | |
859 | ||
860 | An editor will be fired up with all the commits in your current branch | |
861 | (ignoring merge commits), which come after the given commit. You can | |
862 | reorder the commits in this list to your heart's content, and you can | |
863 | remove them. The list looks more or less like this: | |
864 | ||
865 | ------------------------------------------- | |
866 | pick deadbee The oneline of this commit | |
867 | pick fa1afe1 The oneline of the next commit | |
868 | ... | |
869 | ------------------------------------------- | |
870 | ||
0b444cdb | 871 | The oneline descriptions are purely for your pleasure; 'git rebase' will |
1b1dce4b JS |
872 | not look at them but at the commit names ("deadbee" and "fa1afe1" in this |
873 | example), so do not delete or edit the names. | |
874 | ||
875 | By replacing the command "pick" with the command "edit", you can tell | |
0b444cdb | 876 | 'git rebase' to stop after applying that commit, so that you can edit |
1b1dce4b JS |
877 | the files and/or the commit message, amend the commit, and continue |
878 | rebasing. | |
879 | ||
71f82465 JS |
880 | To interrupt the rebase (just like an "edit" command would do, but without |
881 | cherry-picking any commit first), use the "break" command. | |
882 | ||
6741aa6c BG |
883 | If you just want to edit the commit message for a commit, replace the |
884 | command "pick" with the command "reword". | |
885 | ||
c9266d58 GR |
886 | To drop a commit, replace the command "pick" with "drop", or just |
887 | delete the matching line. | |
888 | ||
1b1dce4b | 889 | If you want to fold two or more commits into one, replace the command |
0205e72f MH |
890 | "pick" for the second and subsequent commits with "squash" or "fixup". |
891 | If the commits had different authors, the folded commit will be | |
892 | attributed to the author of the first commit. The suggested commit | |
2c0aa2ce CM |
893 | message for the folded commit is the concatenation of the first |
894 | commit's message with those identified by "squash" commands, omitting the | |
895 | messages of commits identified by "fixup" commands, unless "fixup -c" | |
896 | is used. In that case the suggested commit message is only the message | |
897 | of the "fixup -c" commit, and an editor is opened allowing you to edit | |
898 | the message. The contents (patch) of the "fixup -c" commit are still | |
899 | incorporated into the folded commit. If there is more than one "fixup -c" | |
fa153c1c | 900 | commit, the message from the final one is used. You can also use |
2c0aa2ce CM |
901 | "fixup -C" to get the same behavior as "fixup -c" except without opening |
902 | an editor. | |
903 | ||
1b1dce4b | 904 | |
0b444cdb | 905 | 'git rebase' will stop when "pick" has been replaced with "edit" or |
6741aa6c BG |
906 | when a command fails due to merge errors. When you are done editing |
907 | and/or resolving conflicts you can continue with `git rebase --continue`. | |
1b1dce4b JS |
908 | |
909 | For example, if you want to reorder the last 5 commits, such that what | |
910 | was HEAD~4 becomes the new HEAD. To achieve that, you would call | |
0b444cdb | 911 | 'git rebase' like this: |
1b1dce4b JS |
912 | |
913 | ---------------------- | |
914 | $ git rebase -i HEAD~5 | |
915 | ---------------------- | |
916 | ||
917 | And move the first patch to the end of the list. | |
918 | ||
7948b49a JS |
919 | You might want to recreate merge commits, e.g. if you have a history |
920 | like this: | |
f09c9b8c JS |
921 | |
922 | ------------------ | |
923 | X | |
924 | \ | |
925 | A---M---B | |
926 | / | |
927 | ---o---O---P---Q | |
928 | ------------------ | |
929 | ||
930 | Suppose you want to rebase the side branch starting at "A" to "Q". Make | |
931 | sure that the current HEAD is "B", and call | |
932 | ||
933 | ----------------------------- | |
7948b49a | 934 | $ git rebase -i -r --onto Q O |
f09c9b8c JS |
935 | ----------------------------- |
936 | ||
cd035b1c MM |
937 | Reordering and editing commits usually creates untested intermediate |
938 | steps. You may want to check that your history editing did not break | |
939 | anything by running a test, or at least recompiling at intermediate | |
940 | points in history by using the "exec" command (shortcut "x"). You may | |
941 | do so by creating a todo list like this one: | |
942 | ||
943 | ------------------------------------------- | |
944 | pick deadbee Implement feature XXX | |
945 | fixup f1a5c00 Fix to feature XXX | |
946 | exec make | |
947 | pick c0ffeee The oneline of the next commit | |
948 | edit deadbab The oneline of the commit after | |
949 | exec cd subdir; make test | |
950 | ... | |
951 | ------------------------------------------- | |
952 | ||
953 | The interactive rebase will stop when a command fails (i.e. exits with | |
954 | non-0 status) to give you an opportunity to fix the problem. You can | |
955 | continue with `git rebase --continue`. | |
956 | ||
957 | The "exec" command launches the command in a shell (the one specified | |
958 | in `$SHELL`, or the default shell if `$SHELL` is not set), so you can | |
959 | use shell features (like "cd", ">", ";" ...). The command is run from | |
960 | the root of the working tree. | |
f0fd889d | 961 | |
c2145384 LK |
962 | ---------------------------------- |
963 | $ git rebase -i --exec "make test" | |
964 | ---------------------------------- | |
965 | ||
966 | This command lets you check that intermediate commits are compilable. | |
967 | The todo list becomes like that: | |
968 | ||
969 | -------------------- | |
970 | pick 5928aea one | |
971 | exec make test | |
972 | pick 04d0fda two | |
973 | exec make test | |
974 | pick ba46169 three | |
975 | exec make test | |
976 | pick f4593f9 four | |
977 | exec make test | |
978 | -------------------- | |
979 | ||
f0fd889d JS |
980 | SPLITTING COMMITS |
981 | ----------------- | |
982 | ||
983 | In interactive mode, you can mark commits with the action "edit". However, | |
0b444cdb | 984 | this does not necessarily mean that 'git rebase' expects the result of this |
f0fd889d JS |
985 | edit to be exactly one commit. Indeed, you can undo the commit, or you can |
986 | add other commits. This can be used to split a commit into two: | |
987 | ||
483bc4f0 | 988 | - Start an interactive rebase with `git rebase -i <commit>^`, where |
f0fd889d JS |
989 | <commit> is the commit you want to split. In fact, any commit range |
990 | will do, as long as it contains that commit. | |
991 | ||
992 | - Mark the commit you want to split with the action "edit". | |
993 | ||
483bc4f0 | 994 | - When it comes to editing that commit, execute `git reset HEAD^`. The |
f0fd889d JS |
995 | effect is that the HEAD is rewound by one, and the index follows suit. |
996 | However, the working tree stays the same. | |
997 | ||
998 | - Now add the changes to the index that you want to have in the first | |
483bc4f0 | 999 | commit. You can use `git add` (possibly interactively) or |
0b444cdb | 1000 | 'git gui' (or both) to do that. |
f0fd889d JS |
1001 | |
1002 | - Commit the now-current index with whatever commit message is appropriate | |
1003 | now. | |
1004 | ||
1005 | - Repeat the last two steps until your working tree is clean. | |
1006 | ||
483bc4f0 | 1007 | - Continue the rebase with `git rebase --continue`. |
f0fd889d JS |
1008 | |
1009 | If you are not absolutely sure that the intermediate revisions are | |
1010 | consistent (they compile, pass the testsuite, etc.) you should use | |
0b444cdb | 1011 | 'git stash' to stash away the not-yet-committed changes |
f0fd889d JS |
1012 | after each commit, test, and amend the commit if fixes are necessary. |
1013 | ||
1014 | ||
90d1c08e TR |
1015 | RECOVERING FROM UPSTREAM REBASE |
1016 | ------------------------------- | |
1017 | ||
1018 | Rebasing (or any other form of rewriting) a branch that others have | |
1019 | based work on is a bad idea: anyone downstream of it is forced to | |
1020 | manually fix their history. This section explains how to do the fix | |
1021 | from the downstream's point of view. The real fix, however, would be | |
1022 | to avoid rebasing the upstream in the first place. | |
1023 | ||
1024 | To illustrate, suppose you are in a situation where someone develops a | |
1025 | 'subsystem' branch, and you are working on a 'topic' that is dependent | |
1026 | on this 'subsystem'. You might end up with a history like the | |
1027 | following: | |
1028 | ||
1029 | ------------ | |
01826066 | 1030 | o---o---o---o---o---o---o---o master |
90d1c08e TR |
1031 | \ |
1032 | o---o---o---o---o subsystem | |
1033 | \ | |
1034 | *---*---* topic | |
1035 | ------------ | |
1036 | ||
1037 | If 'subsystem' is rebased against 'master', the following happens: | |
1038 | ||
1039 | ------------ | |
1040 | o---o---o---o---o---o---o---o master | |
1041 | \ \ | |
1042 | o---o---o---o---o o'--o'--o'--o'--o' subsystem | |
1043 | \ | |
1044 | *---*---* topic | |
1045 | ------------ | |
1046 | ||
1047 | If you now continue development as usual, and eventually merge 'topic' | |
1048 | to 'subsystem', the commits from 'subsystem' will remain duplicated forever: | |
1049 | ||
1050 | ------------ | |
1051 | o---o---o---o---o---o---o---o master | |
1052 | \ \ | |
1053 | o---o---o---o---o o'--o'--o'--o'--o'--M subsystem | |
1054 | \ / | |
1055 | *---*---*-..........-*--* topic | |
1056 | ------------ | |
1057 | ||
1058 | Such duplicates are generally frowned upon because they clutter up | |
1059 | history, making it harder to follow. To clean things up, you need to | |
1060 | transplant the commits on 'topic' to the new 'subsystem' tip, i.e., | |
1061 | rebase 'topic'. This becomes a ripple effect: anyone downstream from | |
1062 | 'topic' is forced to rebase too, and so on! | |
1063 | ||
1064 | There are two kinds of fixes, discussed in the following subsections: | |
1065 | ||
1066 | Easy case: The changes are literally the same.:: | |
1067 | ||
1068 | This happens if the 'subsystem' rebase was a simple rebase and | |
1069 | had no conflicts. | |
1070 | ||
1071 | Hard case: The changes are not the same.:: | |
1072 | ||
1073 | This happens if the 'subsystem' rebase had conflicts, or used | |
6cf378f0 JK |
1074 | `--interactive` to omit, edit, squash, or fixup commits; or |
1075 | if the upstream used one of `commit --amend`, `reset`, or | |
9df53c5d EN |
1076 | a full history rewriting command like |
1077 | https://github.com/newren/git-filter-repo[`filter-repo`]. | |
90d1c08e TR |
1078 | |
1079 | ||
1080 | The easy case | |
1081 | ~~~~~~~~~~~~~ | |
1082 | ||
1083 | Only works if the changes (patch IDs based on the diff contents) on | |
1084 | 'subsystem' are literally the same before and after the rebase | |
1085 | 'subsystem' did. | |
1086 | ||
0b444cdb | 1087 | In that case, the fix is easy because 'git rebase' knows to skip |
0fcb4f6b JT |
1088 | changes that are already present in the new upstream (unless |
1089 | `--reapply-cherry-picks` is given). So if you say | |
90d1c08e TR |
1090 | (assuming you're on 'topic') |
1091 | ------------ | |
1092 | $ git rebase subsystem | |
1093 | ------------ | |
1094 | you will end up with the fixed history | |
1095 | ------------ | |
1096 | o---o---o---o---o---o---o---o master | |
1097 | \ | |
1098 | o'--o'--o'--o'--o' subsystem | |
1099 | \ | |
1100 | *---*---* topic | |
1101 | ------------ | |
1102 | ||
1103 | ||
1104 | The hard case | |
1105 | ~~~~~~~~~~~~~ | |
1106 | ||
1107 | Things get more complicated if the 'subsystem' changes do not exactly | |
1108 | correspond to the ones before the rebase. | |
1109 | ||
1110 | NOTE: While an "easy case recovery" sometimes appears to be successful | |
1111 | even in the hard case, it may have unintended consequences. For | |
1112 | example, a commit that was removed via `git rebase | |
6cf378f0 | 1113 | --interactive` will be **resurrected**! |
90d1c08e | 1114 | |
0b444cdb | 1115 | The idea is to manually tell 'git rebase' "where the old 'subsystem' |
414d924b | 1116 | ended and your 'topic' began", that is, what the old merge base |
90d1c08e TR |
1117 | between them was. You will have to find a way to name the last commit |
1118 | of the old 'subsystem', for example: | |
1119 | ||
0b444cdb | 1120 | * With the 'subsystem' reflog: after 'git fetch', the old tip of |
6cf378f0 | 1121 | 'subsystem' is at `subsystem@{1}`. Subsequent fetches will |
90d1c08e TR |
1122 | increase the number. (See linkgit:git-reflog[1].) |
1123 | ||
1124 | * Relative to the tip of 'topic': knowing that your 'topic' has three | |
1125 | commits, the old tip of 'subsystem' must be `topic~3`. | |
1126 | ||
1127 | You can then transplant the old `subsystem..topic` to the new tip by | |
1128 | saying (for the reflog case, and assuming you are on 'topic' already): | |
1129 | ------------ | |
1130 | $ git rebase --onto subsystem subsystem@{1} | |
1131 | ------------ | |
1132 | ||
1133 | The ripple effect of a "hard case" recovery is especially bad: | |
1134 | 'everyone' downstream from 'topic' will now have to perform a "hard | |
1135 | case" recovery too! | |
1136 | ||
25cff9f1 | 1137 | REBASING MERGES |
81d395cc | 1138 | --------------- |
25cff9f1 JS |
1139 | |
1140 | The interactive rebase command was originally designed to handle | |
1141 | individual patch series. As such, it makes sense to exclude merge | |
1142 | commits from the todo list, as the developer may have merged the | |
1143 | then-current `master` while working on the branch, only to rebase | |
1144 | all the commits onto `master` eventually (skipping the merge | |
1145 | commits). | |
1146 | ||
1147 | However, there are legitimate reasons why a developer may want to | |
1148 | recreate merge commits: to keep the branch structure (or "commit | |
1149 | topology") when working on multiple, inter-related branches. | |
1150 | ||
1151 | In the following example, the developer works on a topic branch that | |
1152 | refactors the way buttons are defined, and on another topic branch | |
1153 | that uses that refactoring to implement a "Report a bug" button. The | |
1154 | output of `git log --graph --format=%s -5` may look like this: | |
1155 | ||
1156 | ------------ | |
1157 | * Merge branch 'report-a-bug' | |
1158 | |\ | |
1159 | | * Add the feedback button | |
1160 | * | Merge branch 'refactor-button' | |
1161 | |\ \ | |
1162 | | |/ | |
1163 | | * Use the Button class for all buttons | |
1164 | | * Extract a generic Button class from the DownloadButton one | |
1165 | ------------ | |
1166 | ||
1167 | The developer might want to rebase those commits to a newer `master` | |
1168 | while keeping the branch topology, for example when the first topic | |
1169 | branch is expected to be integrated into `master` much earlier than the | |
1170 | second one, say, to resolve merge conflicts with changes to the | |
1171 | DownloadButton class that made it into `master`. | |
1172 | ||
1173 | This rebase can be performed using the `--rebase-merges` option. | |
1174 | It will generate a todo list looking like this: | |
1175 | ||
1176 | ------------ | |
1177 | label onto | |
1178 | ||
1179 | # Branch: refactor-button | |
1180 | reset onto | |
1181 | pick 123456 Extract a generic Button class from the DownloadButton one | |
1182 | pick 654321 Use the Button class for all buttons | |
1183 | label refactor-button | |
1184 | ||
1185 | # Branch: report-a-bug | |
1186 | reset refactor-button # Use the Button class for all buttons | |
1187 | pick abcdef Add the feedback button | |
1188 | label report-a-bug | |
1189 | ||
1190 | reset onto | |
1191 | merge -C a1b2c3 refactor-button # Merge 'refactor-button' | |
1192 | merge -C 6f5e4d report-a-bug # Merge 'report-a-bug' | |
1193 | ------------ | |
1194 | ||
1195 | In contrast to a regular interactive rebase, there are `label`, `reset` | |
1196 | and `merge` commands in addition to `pick` ones. | |
1197 | ||
1198 | The `label` command associates a label with the current HEAD when that | |
1199 | command is executed. These labels are created as worktree-local refs | |
1200 | (`refs/rewritten/<label>`) that will be deleted when the rebase | |
1201 | finishes. That way, rebase operations in multiple worktrees linked to | |
1202 | the same repository do not interfere with one another. If the `label` | |
1203 | command fails, it is rescheduled immediately, with a helpful message how | |
1204 | to proceed. | |
1205 | ||
1206 | The `reset` command resets the HEAD, index and worktree to the specified | |
ad0b8f95 | 1207 | revision. It is similar to an `exec git reset --hard <label>`, but |
25cff9f1 JS |
1208 | refuses to overwrite untracked files. If the `reset` command fails, it is |
1209 | rescheduled immediately, with a helpful message how to edit the todo list | |
1210 | (this typically happens when a `reset` command was inserted into the todo | |
1211 | list manually and contains a typo). | |
1212 | ||
caafecfc JS |
1213 | The `merge` command will merge the specified revision(s) into whatever |
1214 | is HEAD at that time. With `-C <original-commit>`, the commit message of | |
25cff9f1 JS |
1215 | the specified merge commit will be used. When the `-C` is changed to |
1216 | a lower-case `-c`, the message will be opened in an editor after a | |
1217 | successful merge so that the user can edit the message. | |
1218 | ||
1219 | If a `merge` command fails for any reason other than merge conflicts (i.e. | |
1220 | when the merge operation did not even start), it is rescheduled immediately. | |
1221 | ||
1222 | At this time, the `merge` command will *always* use the `recursive` | |
caafecfc | 1223 | merge strategy for regular merges, and `octopus` for octopus merges, |
57e9dcaa | 1224 | with no way to choose a different one. To work around |
25cff9f1 JS |
1225 | this, an `exec` command can be used to call `git merge` explicitly, |
1226 | using the fact that the labels are worktree-local refs (the ref | |
1227 | `refs/rewritten/onto` would correspond to the label `onto`, for example). | |
1228 | ||
1229 | Note: the first command (`label onto`) labels the revision onto which | |
1230 | the commits are rebased; The name `onto` is just a convention, as a nod | |
1231 | to the `--onto` option. | |
1232 | ||
1233 | It is also possible to introduce completely new merge commits from scratch | |
1234 | by adding a command of the form `merge <merge-head>`. This form will | |
1235 | generate a tentative commit message and always open an editor to let the | |
1236 | user edit it. This can be useful e.g. when a topic branch turns out to | |
1237 | address more than a single concern and wants to be split into two or | |
1238 | even more topic branches. Consider this todo list: | |
1239 | ||
1240 | ------------ | |
1241 | pick 192837 Switch from GNU Makefiles to CMake | |
1242 | pick 5a6c7e Document the switch to CMake | |
1243 | pick 918273 Fix detection of OpenSSL in CMake | |
1244 | pick afbecd http: add support for TLS v1.3 | |
1245 | pick fdbaec Fix detection of cURL in CMake on Windows | |
1246 | ------------ | |
1247 | ||
1248 | The one commit in this list that is not related to CMake may very well | |
1249 | have been motivated by working on fixing all those bugs introduced by | |
1250 | switching to CMake, but it addresses a different concern. To split this | |
1251 | branch into two topic branches, the todo list could be edited like this: | |
1252 | ||
1253 | ------------ | |
1254 | label onto | |
1255 | ||
1256 | pick afbecd http: add support for TLS v1.3 | |
1257 | label tlsv1.3 | |
1258 | ||
1259 | reset onto | |
1260 | pick 192837 Switch from GNU Makefiles to CMake | |
1261 | pick 918273 Fix detection of OpenSSL in CMake | |
1262 | pick fdbaec Fix detection of cURL in CMake on Windows | |
1263 | pick 5a6c7e Document the switch to CMake | |
1264 | label cmake | |
1265 | ||
1266 | reset onto | |
1267 | merge tlsv1.3 | |
1268 | merge cmake | |
1269 | ------------ | |
1270 | ||
414abf15 ÆAB |
1271 | CONFIGURATION |
1272 | ------------- | |
1273 | ||
1274 | include::config/rebase.txt[] | |
1275 | include::config/sequencer.txt[] | |
1276 | ||
cddb42d2 JN |
1277 | BUGS |
1278 | ---- | |
427c3bd2 JS |
1279 | The todo list presented by the deprecated `--preserve-merges --interactive` |
1280 | does not represent the topology of the revision graph (use `--rebase-merges` | |
1281 | instead). Editing commits and rewording their commit messages should work | |
1282 | fine, but attempts to reorder commits tend to produce counterintuitive results. | |
1283 | Use `--rebase-merges` in such scenarios instead. | |
cddb42d2 JN |
1284 | |
1285 | For example, an attempt to rearrange | |
1286 | ------------ | |
1287 | 1 --- 2 --- 3 --- 4 --- 5 | |
1288 | ------------ | |
1289 | to | |
1290 | ------------ | |
1291 | 1 --- 2 --- 4 --- 3 --- 5 | |
1292 | ------------ | |
1293 | by moving the "pick 4" line will result in the following history: | |
1294 | ------------ | |
1295 | 3 | |
1296 | / | |
1297 | 1 --- 2 --- 4 --- 5 | |
1298 | ------------ | |
1299 | ||
7fc9d69f JH |
1300 | GIT |
1301 | --- | |
9e1f0a85 | 1302 | Part of the linkgit:git[1] suite |