When using git stash be aware that git stash pop will literally pop the stashed changes out of the storage, so you won't be able to pop it again later.
You may prefer to git stash list to see all your previously stashed states and then git stash apply stash@{X}(where X is the stash you want to pop back up).
This way the stashed code stays in the stash store as well as being applied, allowing you to later git stash apply again or git stash drop stash@{X} when you're definitely done.
Thank you for stopping by! I am a full-stack developer that combines the power of entrepreneurship and programming to make the lives of programmers easier.
Thanks for the more in-depth explanation! I covered git stash apply a bit in the video but didn't explain about git stash drop.
One more useful feature I'd like to add, since we are expanding on this, is naming your stashes using git stash save "Name or message of the feature" since it can really get confusing with just the name of the commit you were working on.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks Sergiu,
When using
git stashbe aware thatgit stash popwill literally pop the stashed changes out of the storage, so you won't be able to pop it again later.You may prefer to
git stash listto see all your previously stashed states and thengit stash apply stash@{X}(where X is the stash you want to pop back up).This way the stashed code stays in the stash store as well as being applied, allowing you to later
git stash applyagain orgit stash drop stash@{X}when you're definitely done.Thanks for the more in-depth explanation! I covered
git stash applya bit in the video but didn't explain aboutgit stash drop.One more useful feature I'd like to add, since we are expanding on this, is naming your stashes using
git stash save "Name or message of the feature"since it can really get confusing with just the name of the commit you were working on.