Git stash records local changes so the working directory can return to a cleaner state. Before using it, run git status and distinguish tracked edits from new untracked files. A default stash does not include untracked files; --include-untracked adds them, while ignored files require separate consideration.

Give a stash a meaningful message and inspect git stash list and git stash show before restoring it. Check the options for displaying untracked content if that content was included. A stash entry is local repository state, not an independent backup or evidence that another computer has received your work.

Use git stash apply when you want to restore changes while retaining the stash entry for inspection. By contrast, pop removes the entry after successful application. Restoring onto changed code can cause conflicts; the manual says a conflicting pop keeps the entry. Do not assume that a command finishing has resolved the edits correctly.

After application, inspect git status, review the resulting changes and run the relevant project checks. The --index option attempts to restore the staged state too, but can fail with conflicts. Keep the saved entry until you have confirmed the result. This guide recommends no clear or forced cleanup and executes no repository changes.