#GIT STASH CHANGES HOW TO#

Note that those entries will then be subject to pruning,Īnd may be impossible to recover (see Examples below for a possible strategy). Since the stash entry is applied on top of theĬommit that was HEAD at the time git stash was run, it restores the originally stashed This is useful if the branch on which you ran git stash push has changed enough that If that succeeds, and is a reference of theįorm it then drops the. Which the was originally created, applies the changes recorded in to Unlike pop, may beĪny commit that looks like a commit created by stash push or stash create.Ĭreates and checks out a new branch named starting from the commit at Like pop, but do not remove the state from the stash list. When no is given, is assumed, otherwise must be a reference (which are stored in the index, where you therefore can no longer apply the changes as However, this can fail, when you have conflicts If the -index option is used, then tries to reinstate not only the working tree’sĬhanges, but also the index’s ones. You need to resolve the conflicts by hand and call git stash drop manually The workingĪpplying the state can fail with conflicts in this case, it is not removed from the Working tree state, i.e., do the inverse operation of git stash push. Remove a single stashed state from the stash list and apply it on top of the current Stash.showPatch config variables to change the default behavior. By default, the command shows the diffstat, but it willĪccept any format known to git diff (e.g., git stash show -p to view the Show the changes recorded in the stash entry as a diff between the stashed contentsĪnd the commit back when the stash entry was first created. The command takes options applicable to the git log command to control what is shown Of the commit the entry was based WIP on submit: 6ebd0e2. Name of the branch that was current when the entry was made, and a short description is the latest entry, is the one before, etc.), the List the stash entries that you currently have. That it cannot take pathspecs, and any non-option arguments form the message. This option is deprecated in favour of git stash push. You can use -no-keep-index to override this.

#GIT STASH CHANGES HOW TO#

See the “Interactive Mode” section of git-add(1) to learn how to The selected changes are then rolled back from Is the same as the index state of your repository, and its worktree contains only theĬhanges you selected interactively. The stash entry is constructed such that its index state With -patch, you can interactively select hunks from the diff between HEAD and the If the -all option is used instead then the ignored files are stashed and cleaned in Then cleaned up with git clean, leaving the working directory in a very clean state. If the -include-untracked option is used, all untracked files are also stashed and

If the -keep-index option is used, all changes already added to the index are left The index entries and working treeįiles are then rolled back to the state in HEAD only for these files, too, leavingįiles that do not match the pathspec intact. States only for the files that match the pathspec.

When pathspec is given to git stash push, the new stash entry records the modified The two exceptions to this are stash -p which acts as alias for stash push -pĪnd pathspecs, which are allowed after a double hyphen - for disambiguation. In this mode, non-option argumentsĪre not allowed to prevent a misspelled subcommand from making an unwanted stashĮntry. The part is optional and gives theĭescription along with the stashed state.įor quickly making a snapshot, you can omit 'push'. Save your local modifications to a new stash entry and roll them back to HEAD (in the The integer n is equivalent to keep-index] Stashes may also be referenced by specifying just the stash index (e.g. The most recently created stash, is the one before it, isĪlso possible). Reflog of this reference and can be named using the usual reflog syntax (e.g. The latest stash you created is stored in refs/stash older stashes are found in the ', but you can give a moreĭescriptive message on the command line when you create one. A stash is by default listed as 'WIP on branchname. Calling git stash without any arguments is equivalent to git stash push. Inspected with git stash show, and restored (potentially on top of a different commit) The modifications stashed away by this command can be listed with git stash list, Modifications away and reverts the working directory to match the HEAD commit. Index, but want to go back to a clean working directory. Use git stash when you want to record the current state of the working directory and the Git-stash - Stash the changes in a dirty working directory away

Git stash changes