Sure, it’s got the commit SHA and message that your work was based off of, but if you’re anything like me, you forgot what you worked on the moment you stashed the changes and opened up that dreaded bug ticket that took hours to finish.

Instead, stashing like this is a lot better when you’re trying to figure out what you actually threw in there:

git stash save "your message here"

Now, your stashes will look a lot cleaner and hopefully help you save some time when pulling information out of there.

$ git stash list
stash@{0}: On shoulda: Updating instructions
stash@{1}: On master: started merge but need to fix #104 first
stash@{2}: On feature1: Adding some stuff

If you need to see what’s been changed for a certain stash, you can simply pass in the treeish for the stash, given in the git stash list output. The stash@{<number>} part shows you how to reference that changeset. Simply pass it into git diff to figure out what was changed: