git list stash

Oranges Authors

3 min read

·

05-03-2025

7

0

Share

Git stash is a powerful tool for temporarily shelving changes you've made to your working directory and index without committing them. This is incredibly useful when you need to switch branches, fix a bug, or handle another task before you're ready to commit your current work. The command git stash list is your key to managing and understanding your stashed changes. Let's explore it in detail.

What is git stash list?

The git stash list command, as its name suggests, displays a list of all your stashed changes. Each stash is given a unique ID, allowing you to easily identify and retrieve specific stashes later. This is crucial for managing multiple stashed changesets, especially in complex projects.

Understanding the Output of git stash list

The output of git stash list typically looks something like this (exact formatting might vary slightly depending on your Git version):

stash@{0}: WIP on master: 04920e5 add feature X
stash@{1}: WIP on master: 7a79c9f fix bug Y

• stash@{0}: This represents the most recently stashed changes. The number in the curly braces increases with each new stash.
• WIP on master: This indicates that the stash was created while working on the master branch. This part reflects the branch you were on when the stash was created. Note that it shows “WIP” which stands for "Work In Progress."
• 04920e5 add feature X: This is a shortened SHA-1 hash of the commit that was your HEAD before the stash was applied, and a brief description of the changes. This description comes from the optional message you can provide during stashing (using git stash push -u -m "your message").

Practical Examples and Analysis

Let's say you're working on "feature X" and suddenly need to quickly fix a critical bug on another branch. You might run:

git stash push -u -m "feature X in progress"

This stashes your current changes for "feature X", including untracked files (-u), and adds a descriptive message. Then you can switch to the bugfix branch.

After fixing the bug and committing the fix, you can use git stash list to see your stashed changes:

git stash list
stash@{0}: WIP on master: feature X in progress

Now you can easily retrieve your "feature X" work using git stash pop stash@{0} or git stash apply stash@{0} (we'll explore the difference between pop and apply in the next section).

git stash pop vs. git stash apply

While both pop and apply restore stashed changes, there's a key difference:

• git stash pop stash@{0}: This applies the stash and then removes it from the stash list. This is generally the preferred method if you're done with the stashed changes.
• git stash apply stash@{0}: This applies the stash but leaves it in the stash list. This is useful if you might need to re-apply the changes later or want to keep a history of your stashed work.

Advanced Usage and Tips

• Filtering Stashes: If you have many stashes, you can use grep to filter git stash list output. For example, git stash list | grep "feature" will only show stashes containing "feature" in their description.
• Dropping Stashes: Use git stash drop stash@{0} to remove a specific stash. git stash clear removes all stashes. Always exercise caution with git stash clear as this action is irreversible.
• Stashing specific files: You can stash specific files using the -p (patch) option with git stash.

Conclusion

git stash list is a simple yet powerful command that gives you a clear overview of your temporarily shelved changes. Mastering its use will significantly improve your workflow and efficiency when working with Git. Remember to always back up your work regularly, and use descriptive messages when stashing changes to make managing your stashes easier. Combining git stash list with other stash commands lets you navigate complex workflows with confidence.