Git stash: Scenarios and Operations for Temporarily Saving Uncommitted Code

Git stash is used to temporarily save uncommitted work progress, solving code management issues when switching branches or handling other tasks. Common scenarios include when an urgent repair for an online bug is needed during development, or when temporarily dealing with a simple task, allowing the current modifications to be safely saved. Core operations: Use `git stash save "message"` to save uncommitted changes; use `git stash list` to view the list of saved stashes; use `git stash pop` (restore and delete) or `git stash apply` (restore and keep) to restore the most recent stash; use `git stash drop` to delete a specific stash, and `git stash clear` to delete all stashes. The `-u` parameter can save untracked files. Note: Stash does not save untracked files; for long-term work progress, it is recommended to use `git commit` to avoid relying on stash. Mastering these operations allows flexible management of the development process and ensures code safety.