Quick answer: Name your stashes, list and inspect them before applying, and prefer apply over pop until you have confirmed, so stashed work is never lost.
Git stash is handy until you lose track of what is in it. A little discipline keeps your work safe. Here is how.
How to fix it
1. Name your stashes
Use git stash push -m with a message so you know what each stash holds.
2. Inspect before applying
List and show stashes so you apply the right one to the right branch.
3. Apply, then drop
Use apply and verify before dropping, so a bad apply does not lose the stash.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.