Clean vs dirty working directory in Git - Visual Side-by-Side Comparison

Process Flow - Clean vs dirty working directory

Start: Working Directory

↓

Check for changes?

↓

Clean

↓

Ready for

This flow shows how Git checks your working directory for changes. If no changes, it's clean; if changes exist, it's dirty.

Execution Sample

Git

git status
# Shows if working directory is clean or dirty

This command checks the current state of your working directory and staging area.

Process Table

Step	Command	Working Directory State	Git Output Summary	Next Action
1	git status	No changes	"working tree clean"	Ready for next commit
2	touch file.txt	New untracked file	"Untracked files:" list shown	Add or ignore file
3	git add file.txt	File staged	"Changes to be committed:" list shown	Commit or unstage
4	echo 'change' > file.txt	Modified staged file	"Changes not staged for commit:" list shown	Add changes or discard
5	git commit -m 'Add file.txt'	No changes	"working tree clean"	Ready for next commit

💡 Execution stops when working directory is clean and no changes are staged.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5
Working Directory	Clean	Dirty (untracked file)	Dirty (file staged)	Dirty (file modified)	Clean
Staging Area	Empty	Empty	file.txt staged	file.txt staged but modified	Empty

Key Moments - 3 Insights

Why does git status show 'working tree clean' even after creating a new file?

Because the new file is untracked and not staged yet, git status shows it under 'Untracked files' but the working tree is not clean until changes are staged or ignored (see execution_table step 2).

What does it mean when git status shows 'Changes to be committed'?

It means files are staged and ready to be committed. This is shown after 'git add' command (see execution_table step 3).

Why does modifying a staged file show 'Changes not staged for commit'?

Because the file was changed after staging, so the staged snapshot differs from the working directory. You need to add again to update the staging area (see execution_table step 4).

Visual Quiz - 3 Questions

Look at the execution table, what is the working directory state after step 3?

A Clean

B Dirty with staged files

C Dirty with untracked files

D Dirty with unstaged changes

💡 Hint

Check the 'Working Directory State' column at step 3 in the execution_table.

At which step does git status show 'working tree clean'?

A Step 1 and Step 5

B Step 2

C Step 3

D Step 4

💡 Hint

Look for 'working tree clean' in the 'Git Output Summary' column in the execution_table.

If you modify a staged file but do not run git add again, what will git status show?

A No changes, working tree clean

B Changes to be committed

C Changes not staged for commit

D Untracked files

💡 Hint

Refer to step 4 in the execution_table where the file is modified after staging.

Concept Snapshot

Clean vs Dirty Working Directory in Git:
- Clean: No changes or all changes committed.
- Dirty: Untracked, modified, or staged changes exist.
- git status shows state: 'working tree clean' means clean.
- Use git add to stage changes.
- Modify after staging requires re-adding to update staging.

Full Transcript

This visual execution shows how Git determines if your working directory is clean or dirty. Starting with no changes, git status reports 'working tree clean'. Creating a new file makes the directory dirty with untracked files. Adding the file stages it, showing 'Changes to be committed'. Modifying the staged file again makes it dirty with unstaged changes. Committing clears all changes, returning to a clean state. Key points include understanding untracked vs staged vs modified states and how git status messages reflect these. This helps you know when your directory is ready for commit or needs more action.