]>
Commit | Line | Data |
---|---|---|
09ccdb63 NS |
1 | git-stash(1) |
2 | ============ | |
3 | ||
4 | NAME | |
5 | ---- | |
6 | git-stash - Stash the changes in a dirty working directory away | |
7 | ||
8 | SYNOPSIS | |
9 | -------- | |
10 | [verse] | |
a5ab00c5 | 11 | 'git stash' list [<options>] |
bef55dcf | 12 | 'git stash' show [<options>] [<stash>] |
fcdd0e92 SB |
13 | 'git stash' drop [-q|--quiet] [<stash>] |
14 | 'git stash' ( pop | apply ) [--index] [-q|--quiet] [<stash>] | |
656b5034 | 15 | 'git stash' branch <branchname> [<stash>] |
1ada5020 | 16 | 'git stash' [push [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] |
0a790f09 | 17 | [-u|--include-untracked] [-a|--all] [-m|--message <message>] |
8a98758a | 18 | [--pathspec-from-file=<file> [--pathspec-file-nul]] |
1ada5020 | 19 | [--] [<pathspec>...]] |
656b5034 | 20 | 'git stash' clear |
2be43516 | 21 | 'git stash' create [<message>] |
bd514cad | 22 | 'git stash' store [-m|--message <message>] [-q|--quiet] <commit> |
09ccdb63 NS |
23 | |
24 | DESCRIPTION | |
25 | ----------- | |
26 | ||
ca768288 | 27 | Use `git stash` when you want to record the current state of the |
09ccdb63 NS |
28 | working directory and the index, but want to go back to a clean |
29 | working directory. The command saves your local modifications away | |
30 | and reverts the working directory to match the `HEAD` commit. | |
31 | ||
32 | The modifications stashed away by this command can be listed with | |
483bc4f0 JN |
33 | `git stash list`, inspected with `git stash show`, and restored |
34 | (potentially on top of a different commit) with `git stash apply`. | |
db37745e | 35 | Calling `git stash` without any arguments is equivalent to `git stash push`. |
483bc4f0 | 36 | A stash is by default listed as "WIP on 'branchname' ...", but |
ec96e0f6 NS |
37 | you can give a more descriptive message on the command line when |
38 | you create one. | |
09ccdb63 | 39 | |
cc1b8d8b | 40 | The latest stash you created is stored in `refs/stash`; older |
9488e875 | 41 | stashes are found in the reflog of this reference and can be named using |
6cf378f0 JK |
42 | the usual reflog syntax (e.g. `stash@{0}` is the most recently |
43 | created stash, `stash@{1}` is the one before it, `stash@{2.hours.ago}` | |
a56c8f5a AW |
44 | is also possible). Stashes may also be referenced by specifying just the |
45 | stash index (e.g. the integer `n` is equivalent to `stash@{n}`). | |
09ccdb63 | 46 | |
0093abc2 AM |
47 | COMMANDS |
48 | -------- | |
09ccdb63 | 49 | |
8a98758a | 50 | push [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [-m|--message <message>] [--pathspec-from-file=<file> [--pathspec-file-nul]] [--] [<pathspec>...]:: |
09ccdb63 | 51 | |
e01db917 | 52 | Save your local modifications to a new 'stash entry' and roll them |
20a7e061 TG |
53 | back to HEAD (in the working tree and in the index). |
54 | The <message> part is optional and gives | |
9e140909 TG |
55 | the description along with the stashed state. |
56 | + | |
57 | For quickly making a snapshot, you can omit "push". In this mode, | |
58 | non-option arguments are not allowed to prevent a misspelled | |
e01db917 | 59 | subcommand from making an unwanted stash entry. The two exceptions to this |
3f3d8068 | 60 | are `stash -p` which acts as alias for `stash push -p` and pathspec elements, |
9e140909 | 61 | which are allowed after a double hyphen `--` for disambiguation. |
09ccdb63 | 62 | |
fd2ebf14 TG |
63 | save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: |
64 | ||
65 | This option is deprecated in favour of 'git stash push'. It | |
3f3d8068 | 66 | differs from "stash push" in that it cannot take pathspec. |
57d8f4b4 JS |
67 | Instead, all non-option arguments are concatenated to form the stash |
68 | message. | |
fd2ebf14 | 69 | |
fbd538c2 | 70 | list [<options>]:: |
09ccdb63 | 71 | |
e01db917 LB |
72 | List the stash entries that you currently have. Each 'stash entry' is |
73 | listed with its name (e.g. `stash@{0}` is the latest entry, `stash@{1}` is | |
9488e875 | 74 | the one before, etc.), the name of the branch that was current when the |
e01db917 | 75 | entry was made, and a short description of the commit the entry was |
09ccdb63 NS |
76 | based on. |
77 | + | |
78 | ---------------------------------------------------------------- | |
ec96e0f6 NS |
79 | stash@{0}: WIP on submit: 6ebd0e2... Update git-stash documentation |
80 | stash@{1}: On master: 9cc0589... Add git-stash | |
09ccdb63 | 81 | ---------------------------------------------------------------- |
fbd538c2 | 82 | + |
0b444cdb | 83 | The command takes options applicable to the 'git log' |
b7b10385 | 84 | command to control what is shown and how. See linkgit:git-log[1]. |
09ccdb63 | 85 | |
bef55dcf | 86 | show [<options>] [<stash>]:: |
09ccdb63 | 87 | |
e01db917 LB |
88 | Show the changes recorded in the stash entry as a diff between the |
89 | stashed contents and the commit back when the stash entry was first | |
0093abc2 | 90 | created. |
e01db917 LB |
91 | By default, the command shows the diffstat, but it will accept any |
92 | format known to 'git diff' (e.g., `git stash show -p stash@{1}` | |
93 | to view the second most recent entry in patch form). | |
3086c064 NK |
94 | You can use stash.showStat and/or stash.showPatch config variables |
95 | to change the default behavior. | |
09ccdb63 | 96 | |
fcdd0e92 | 97 | pop [--index] [-q|--quiet] [<stash>]:: |
09ccdb63 | 98 | |
d1836637 TR |
99 | Remove a single stashed state from the stash list and apply it |
100 | on top of the current working tree state, i.e., do the inverse | |
db37745e | 101 | operation of `git stash push`. The working directory must |
d1836637 | 102 | match the index. |
9488e875 | 103 | + |
d1836637 TR |
104 | Applying the state can fail with conflicts; in this case, it is not |
105 | removed from the stash list. You need to resolve the conflicts by hand | |
106 | and call `git stash drop` manually afterwards. | |
f39d6ee2 | 107 | |
fcdd0e92 | 108 | apply [--index] [-q|--quiet] [<stash>]:: |
f39d6ee2 | 109 | |
b0c6bf4a JS |
110 | Like `pop`, but do not remove the state from the stash list. Unlike `pop`, |
111 | `<stash>` may be any commit that looks like a commit created by | |
db37745e | 112 | `stash push` or `stash create`. |
09ccdb63 | 113 | |
656b5034 AMS |
114 | branch <branchname> [<stash>]:: |
115 | ||
116 | Creates and checks out a new branch named `<branchname>` starting from | |
117 | the commit at which the `<stash>` was originally created, applies the | |
b0c6bf4a JS |
118 | changes recorded in `<stash>` to the new working tree and index. |
119 | If that succeeds, and `<stash>` is a reference of the form | |
0093abc2 | 120 | `stash@{<revision>}`, it then drops the `<stash>`. |
656b5034 | 121 | + |
db37745e | 122 | This is useful if the branch on which you ran `git stash push` has |
656b5034 | 123 | changed enough that `git stash apply` fails due to conflicts. Since |
e01db917 LB |
124 | the stash entry is applied on top of the commit that was HEAD at the |
125 | time `git stash` was run, it restores the originally stashed state | |
126 | with no conflicts. | |
656b5034 | 127 | |
09ccdb63 | 128 | clear:: |
e01db917 | 129 | Remove all the stash entries. Note that those entries will then |
f5f1e164 TR |
130 | be subject to pruning, and may be impossible to recover (see |
131 | 'Examples' below for a possible strategy). | |
09ccdb63 | 132 | |
fcdd0e92 | 133 | drop [-q|--quiet] [<stash>]:: |
e25d5f9c | 134 | |
e01db917 | 135 | Remove a single stash entry from the list of stash entries. |
e25d5f9c | 136 | |
a5ab00c5 SB |
137 | create:: |
138 | ||
e01db917 LB |
139 | Create a stash entry (which is a regular commit object) and |
140 | return its object name, without storing it anywhere in the ref | |
141 | namespace. | |
2be43516 | 142 | This is intended to be useful for scripts. It is probably not |
0d5f844f | 143 | the command you want to use; see "push" above. |
a5ab00c5 | 144 | |
bd514cad RR |
145 | store:: |
146 | ||
147 | Store a given stash created via 'git stash create' (which is a | |
148 | dangling merge commit) in the stash ref, updating the stash | |
149 | reflog. This is intended to be useful for scripts. It is | |
0d5f844f | 150 | probably not the command you want to use; see "push" above. |
09ccdb63 | 151 | |
0093abc2 AM |
152 | OPTIONS |
153 | ------- | |
154 | -a:: | |
155 | --all:: | |
156 | This option is only valid for `push` and `save` commands. | |
157 | + | |
158 | All ignored and untracked files are also stashed and then cleaned | |
159 | up with `git clean`. | |
2b7460d1 | 160 | |
0093abc2 AM |
161 | -u:: |
162 | --include-untracked:: | |
163 | This option is only valid for `push` and `save` commands. | |
164 | + | |
165 | All untracked files are also stashed and then cleaned up with | |
166 | `git clean`. | |
2b7460d1 | 167 | |
0093abc2 AM |
168 | --index:: |
169 | This option is only valid for `pop` and `apply` commands. | |
170 | + | |
171 | Tries to reinstate not only the working tree's changes, but also | |
172 | the index's ones. However, this can fail, when you have conflicts | |
173 | (which are stored in the index, where you therefore can no longer | |
174 | apply the changes as they were originally). | |
175 | ||
176 | -k:: | |
177 | --keep-index:: | |
178 | --no-keep-index:: | |
179 | This option is only valid for `push` and `save` commands. | |
180 | + | |
181 | All changes already added to the index are left intact. | |
2b7460d1 | 182 | |
0093abc2 AM |
183 | -p:: |
184 | --patch:: | |
185 | This option is only valid for `push` and `save` commands. | |
186 | + | |
187 | Interactively select hunks from the diff between HEAD and the | |
188 | working tree to be stashed. The stash entry is constructed such | |
189 | that its index state is the same as the index state of your | |
190 | repository, and its worktree contains only the changes you selected | |
191 | interactively. The selected changes are then rolled back from your | |
192 | worktree. See the ``Interactive Mode'' section of linkgit:git-add[1] | |
193 | to learn how to operate the `--patch` mode. | |
2b7460d1 AM |
194 | + |
195 | The `--patch` option implies `--keep-index`. You can use | |
196 | `--no-keep-index` to override this. | |
197 | ||
8a98758a AM |
198 | --pathspec-from-file=<file>:: |
199 | This option is only valid for `push` command. | |
200 | + | |
201 | Pathspec is passed in `<file>` instead of commandline args. If | |
202 | `<file>` is exactly `-` then standard input is used. Pathspec | |
203 | elements are separated by LF or CR/LF. Pathspec elements can be | |
204 | quoted as explained for the configuration variable `core.quotePath` | |
205 | (see linkgit:git-config[1]). See also `--pathspec-file-nul` and | |
206 | global `--literal-pathspecs`. | |
207 | ||
208 | --pathspec-file-nul:: | |
209 | This option is only valid for `push` command. | |
210 | + | |
211 | Only meaningful with `--pathspec-from-file`. Pathspec elements are | |
212 | separated with NUL character and all other characters are taken | |
213 | literally (including newlines and quotes). | |
214 | ||
b2290914 AM |
215 | -q:: |
216 | --quiet:: | |
217 | This option is only valid for `apply`, `drop`, `pop`, `push`, | |
218 | `save`, `store` commands. | |
219 | + | |
220 | Quiet, suppress feedback messages. | |
221 | ||
222 | \--:: | |
223 | This option is only valid for `push` command. | |
224 | + | |
225 | Separates pathspec from options for disambiguation purposes. | |
226 | ||
0093abc2 AM |
227 | <pathspec>...:: |
228 | This option is only valid for `push` command. | |
229 | + | |
230 | The new stash entry records the modified states only for the files | |
231 | that match the pathspec. The index entries and working tree files | |
232 | are then rolled back to the state in HEAD only for these files, | |
233 | too, leaving files that do not match the pathspec intact. | |
3f3d8068 AM |
234 | + |
235 | For more details, see the 'pathspec' entry in linkgit:gitglossary[7]. | |
0093abc2 AM |
236 | |
237 | <stash>:: | |
238 | This option is only valid for `apply`, `branch`, `drop`, `pop`, | |
239 | `show` commands. | |
240 | + | |
241 | A reference of the form `stash@{<revision>}`. When no `<stash>` is | |
242 | given, the latest stash is assumed (that is, `stash@{0}`). | |
2b7460d1 | 243 | |
09ccdb63 NS |
244 | DISCUSSION |
245 | ---------- | |
246 | ||
e01db917 LB |
247 | A stash entry is represented as a commit whose tree records the state |
248 | of the working directory, and its first parent is the commit at `HEAD` | |
249 | when the entry was created. The tree of the second parent records the | |
250 | state of the index when the entry is made, and it is made a child of | |
09ccdb63 NS |
251 | the `HEAD` commit. The ancestry graph looks like this: |
252 | ||
253 | .----W | |
254 | / / | |
114fd812 | 255 | -----H----I |
09ccdb63 NS |
256 | |
257 | where `H` is the `HEAD` commit, `I` is a commit that records the state | |
258 | of the index, and `W` is a commit that records the state of the working | |
259 | tree. | |
260 | ||
261 | ||
262 | EXAMPLES | |
263 | -------- | |
264 | ||
265 | Pulling into a dirty tree:: | |
266 | ||
267 | When you are in the middle of something, you learn that there are | |
9488e875 JH |
268 | upstream changes that are possibly relevant to what you are |
269 | doing. When your local changes do not conflict with the changes in | |
09ccdb63 NS |
270 | the upstream, a simple `git pull` will let you move forward. |
271 | + | |
272 | However, there are cases in which your local changes do conflict with | |
273 | the upstream changes, and `git pull` refuses to overwrite your | |
9488e875 | 274 | changes. In such a case, you can stash your changes away, |
09ccdb63 NS |
275 | perform a pull, and then unstash, like this: |
276 | + | |
277 | ---------------------------------------------------------------- | |
278 | $ git pull | |
9da6f0ff | 279 | ... |
09ccdb63 NS |
280 | file foobar not up to date, cannot merge. |
281 | $ git stash | |
282 | $ git pull | |
d1836637 | 283 | $ git stash pop |
09ccdb63 NS |
284 | ---------------------------------------------------------------- |
285 | ||
286 | Interrupted workflow:: | |
287 | ||
288 | When you are in the middle of something, your boss comes in and | |
9488e875 | 289 | demands that you fix something immediately. Traditionally, you would |
09ccdb63 | 290 | make a commit to a temporary branch to store your changes away, and |
9488e875 | 291 | return to your original branch to make the emergency fix, like this: |
09ccdb63 NS |
292 | + |
293 | ---------------------------------------------------------------- | |
9da6f0ff | 294 | # ... hack hack hack ... |
328c6cb8 | 295 | $ git switch -c my_wip |
09ccdb63 | 296 | $ git commit -a -m "WIP" |
328c6cb8 | 297 | $ git switch master |
09ccdb63 NS |
298 | $ edit emergency fix |
299 | $ git commit -a -m "Fix in a hurry" | |
328c6cb8 | 300 | $ git switch my_wip |
09ccdb63 | 301 | $ git reset --soft HEAD^ |
9da6f0ff | 302 | # ... continue hacking ... |
09ccdb63 NS |
303 | ---------------------------------------------------------------- |
304 | + | |
0b444cdb | 305 | You can use 'git stash' to simplify the above, like this: |
09ccdb63 NS |
306 | + |
307 | ---------------------------------------------------------------- | |
9da6f0ff | 308 | # ... hack hack hack ... |
09ccdb63 NS |
309 | $ git stash |
310 | $ edit emergency fix | |
311 | $ git commit -a -m "Fix in a hurry" | |
d1836637 | 312 | $ git stash pop |
9da6f0ff | 313 | # ... continue hacking ... |
09ccdb63 NS |
314 | ---------------------------------------------------------------- |
315 | ||
7bedebca SG |
316 | Testing partial commits:: |
317 | ||
db37745e | 318 | You can use `git stash push --keep-index` when you want to make two or |
7bedebca SG |
319 | more commits out of the changes in the work tree, and you want to test |
320 | each change before committing: | |
321 | + | |
322 | ---------------------------------------------------------------- | |
9da6f0ff | 323 | # ... hack hack hack ... |
caf18996 | 324 | $ git add --patch foo # add just first part to the index |
db37745e | 325 | $ git stash push --keep-index # save all other changes to the stash |
caf18996 | 326 | $ edit/build/test first part |
f733c709 | 327 | $ git commit -m 'First part' # commit fully tested change |
caf18996 | 328 | $ git stash pop # prepare to work on all other changes |
9da6f0ff | 329 | # ... repeat above five steps until one commit remains ... |
caf18996 ER |
330 | $ edit/build/test remaining parts |
331 | $ git commit foo -m 'Remaining parts' | |
7bedebca SG |
332 | ---------------------------------------------------------------- |
333 | ||
e01db917 | 334 | Recovering stash entries that were cleared/dropped erroneously:: |
f5f1e164 | 335 | |
e01db917 | 336 | If you mistakenly drop or clear stash entries, they cannot be recovered |
f5f1e164 | 337 | through the normal safety mechanisms. However, you can try the |
e01db917 LB |
338 | following incantation to get a list of stash entries that are still in |
339 | your repository, but not reachable any more: | |
f5f1e164 TR |
340 | + |
341 | ---------------------------------------------------------------- | |
342 | git fsck --unreachable | | |
343 | grep commit | cut -d\ -f3 | | |
344 | xargs git log --merges --no-walk --grep=WIP | |
345 | ---------------------------------------------------------------- | |
346 | ||
347 | ||
09ccdb63 NS |
348 | SEE ALSO |
349 | -------- | |
5162e697 DM |
350 | linkgit:git-checkout[1], |
351 | linkgit:git-commit[1], | |
352 | linkgit:git-reflog[1], | |
328c6cb8 NTND |
353 | linkgit:git-reset[1], |
354 | linkgit:git-switch[1] | |
09ccdb63 | 355 | |
09ccdb63 NS |
356 | GIT |
357 | --- | |
9e1f0a85 | 358 | Part of the linkgit:git[1] suite |