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