I often start working on a certain branch (e.g. new-feature) and get interrupted by something with a higher priority (e.g. high-prio). Most of the time, my changes on new-feature are incomplete and therefore I don't want to do a full commit¹, so I git stash them before checking out a new high-prio branch. This creates a new stash which is associated with new-feature:
stash@{0}: WIP on new-feature: <sha1 and message of previous commit>
Now, I can complete my work on high-prio. After I'm done with that I checkout new-feature again and (since it has been a while) often forget that there was a stash associated with this branch. This creates problems as I might re-do work I already completed on the stash or I have to merge / rebase those changes later.
Is there a configuration setting which reminds me about the existing stash or, even better, automatically pops the stash back into my working tree after checking out new-feature again?
¹ Doing a "WIP"-Commit and later squashing the changes is not a good solution because I want to always keep origin/new-feature in sync with my local new-feature.