Git stash: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 4: | Line 4: | ||
=Overview= | =Overview= | ||
Stash the changes in a dirty working directory away. The command saves the local modifications away and reverts the working directory to match the HEAD commit. | Stash the changes in a dirty working directory away. The command saves the local modifications away and reverts the working directory to match the HEAD commit. The modifications are saved in bulk, it is not possible to choose individual files. | ||
To stash away changes: | To stash away changes: |
Revision as of 06:04, 2 September 2020
Internal
Overview
Stash the changes in a dirty working directory away. The command saves the local modifications away and reverts the working directory to match the HEAD commit. The modifications are saved in bulk, it is not possible to choose individual files.
To stash away changes:
git stash Saved working directory and index state WIP on branch-name: 0d0178916ee commit comment
The modifications stashed away can be listed with:
git stash list
To see the files affected by the stash:
git stash show
They can be restored, potentially in top of a different commit, with:
git stash apply
Without an argument, "apply" applies the content set at the top of the stack (the latest).
Note that the stash state stays on the stack - to remove it:
git stash drop
To remove an arbitrary stash state:
git stash drop <number>
This clears all stash entries:
git stash clear