git stash to save changes - Step-by-Step Execution

Process Flow - git stash to save changes

Make changes in files

↓

Run 'git stash'

↓

Changes saved in stash

↓

Working directory clean

↓

Later: Run 'git stash apply' or 'git stash pop'

↓

Changes restored to working directory

You save your current changes safely with 'git stash', clean your workspace, and later restore those changes when ready.

Execution Sample

Git

git stash
# saves changes and cleans working directory

git stash list
# shows saved stashes

git stash apply
# reapplies last stash

This sequence saves your current changes, lists saved stashes, and reapplies the last saved changes.

Process Table

Step	Command	Action	Result	Working Directory State
1	Modify files (e.g., edit file.txt)	Change detected	Files modified but not committed	Uncommitted changes present
2	git stash	Save changes to stash	Changes saved, working directory cleaned	No uncommitted changes
3	git stash list	Show stash entries	One stash entry listed	Working directory clean
4	git stash apply	Reapply last stash	Changes restored to files	Uncommitted changes present
5	git stash drop	Remove stash entry	Stash entry deleted	Uncommitted changes remain
6	git stash pop	Reapply and drop stash	Changes restored and stash removed	Uncommitted changes present
7	git stash list	Show stash entries	No stash entries	Working directory state unchanged
8	-	No more stashes	No action	Working directory state unchanged

💡 No more stash entries to apply or list

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	After Step 6	Final
Working Directory	Clean	Modified files present	Clean (changes stashed)	Modified files restored	Modified files restored	Modified files restored
Stash List	Empty	Empty	One stash entry	One stash entry	Empty (after pop)	Empty

Key Moments - 3 Insights

Why does 'git stash' make my working directory clean?

'git stash' saves your changes safely and removes them from the working directory, so it looks clean as shown in step 2 of the execution_table.

What is the difference between 'git stash apply' and 'git stash pop'?

'git stash apply' restores changes but keeps the stash entry (step 4), while 'git stash pop' restores changes and deletes the stash entry (step 6).

Why might I see no stash entries after 'git stash pop'?

Because 'git stash pop' reapplies and removes the stash entry, leaving the stash list empty as shown in step 7.

Visual Quiz - 3 Questions

Look at the execution_table at step 2. What is the state of the working directory after running 'git stash'?

A It is clean with no uncommitted changes

B It still has uncommitted changes

C It has committed changes only

D It is deleted

💡 Hint

Check the 'Working Directory State' column at step 2 in the execution_table

At which step does the stash list become empty again after having entries?

A Step 4

B Step 5

C Step 7

D Step 6

💡 Hint

Look at the 'Stash List' variable in variable_tracker and the 'Result' column in execution_table

If you want to restore changes but keep the stash for later, which command should you use?

A git stash pop

B git stash apply

C git stash drop

D git stash list

💡 Hint

Refer to the difference explained in key_moments between 'apply' and 'pop'

Concept Snapshot

git stash saves your current uncommitted changes safely.
It cleans your working directory so you can work on something else.
Use 'git stash apply' to restore changes without deleting stash.
Use 'git stash pop' to restore and delete stash entry.
Check saved stashes with 'git stash list'.

Full Transcript

This visual execution shows how 'git stash' saves your current changes and cleans your working directory. You start by modifying files, then run 'git stash' to save those changes safely. The working directory becomes clean, allowing you to switch tasks. Later, you can use 'git stash apply' to restore changes without removing the stash, or 'git stash pop' to restore and delete the stash entry. The stash list shows saved entries and updates as you apply or drop stashes. This helps keep your work safe and organized.