Clean vs dirty working directory in Git - When to Use Which

The Big Idea

Ever sent unfinished work because you didn't know what files were changed?

The Scenario

Imagine you are working on a group project and you have many files open and changed on your computer. You want to share your work, but you are not sure which files you have changed and which are still the original ones.

The Problem

Manually checking each file to see if it has changed is slow and confusing. You might forget to save some changes or accidentally share unfinished work. This can cause mistakes and waste time fixing problems later.

The Solution

Git shows you if your working directory is clean or dirty. A clean directory means all changes are saved and ready. A dirty directory means you have unsaved or untracked changes. This helps you know exactly what needs attention before sharing.

Before vs After

✗ Before

open each file and check for changes

✓ After

git status

What It Enables

This lets you confidently manage your work and avoid errors by knowing the exact state of your files at any time.

Real Life Example

Before sending your project to a teammate, you run git status to see if you forgot to save or add any files. This prevents sending incomplete or broken work.

Key Takeaways

Manual file checks are slow and error-prone.

Git tells you if your working directory is clean or dirty.

This helps you manage changes safely and efficiently.

Practice

1. What does it mean when your Git working directory is described as clean?

easy

A. There are conflicts from a merge.

B. There are untracked files present.

C. There are changes staged but not committed.

D. There are no changes to commit; all files are saved in Git.

Solution

1. Step 1: Understand the meaning of a clean working directory

   A clean working directory means no changes are pending to be committed or staged.

2. Step 2: Compare with other states

   Untracked files, staged changes, or conflicts mean the directory is dirty, not clean.

3. Final Answer:

   There are no changes to commit; all files are saved in Git. -> Option D

4. Quick Check:

   Clean working directory = no uncommitted changes [OK]

Hint: Clean means no changes to commit or stage [OK]

Common Mistakes:

• Confusing staged changes with clean state
• Thinking untracked files mean clean
• Assuming conflicts mean clean

2. Which Git command correctly shows the current state of your working directory?

easy

A. git push origin main

B. git commit -m "status"

C. git status

D. git checkout

Solution

1. Step 1: Identify the command to check working directory state

   The command git status shows staged, unstaged, and untracked changes.

2. Step 2: Eliminate other commands

   git commit saves changes, git push uploads commits, git checkout switches branches or files.

3. Final Answer:

   git status -> Option C

4. Quick Check:

   Check working directory state = git status [OK]

Hint: Use 'git status' to see working directory changes [OK]

Common Mistakes:

• Using git commit to check status
• Confusing git push with status check
• Using git checkout incorrectly

3. You run git status and see:

Changes not staged for commit:
  modified:   app.js

What is the state of your working directory?

medium

A. Dirty working directory with unstaged changes

B. Dirty working directory with staged changes

C. Clean working directory

D. Detached HEAD state

Solution

1. Step 1: Interpret the git status output

   The message "Changes not staged for commit" means files are modified but not added to staging.

2. Step 2: Determine working directory state

   Unstaged changes mean the directory is dirty, not clean, and changes are not staged.

3. Final Answer:

   Dirty working directory with unstaged changes -> Option A

4. Quick Check:

   Unstaged changes = dirty directory [OK]

Hint: Unstaged changes mean dirty directory [OK]

Common Mistakes:

• Confusing unstaged with staged changes
• Assuming clean when files are modified
• Mixing detached HEAD with working directory state

4. You see this output after running git status:

On branch main
Changes to be committed:
  modified:   index.html

But you want to check if your working directory is clean. What should you do?

medium

A. Run git reset HEAD index.html to unstage changes

B. Run git commit to save changes

C. Run git add index.html again

D. Run git checkout index.html to stage changes

Solution

1. Step 1: Understand the meaning of staged changes

   "Changes to be committed" means files are staged but not committed, so directory is dirty.

2. Step 2: Unstage changes to check clean state

   Running git reset HEAD index.html unstages the file, showing if working directory has unstaged changes.

3. Final Answer:

   Run git reset HEAD index.html to unstage changes -> Option A

4. Quick Check:

   Unstage changes to check clean state [OK]

Hint: Unstage files with git reset HEAD to check clean state [OK]

Common Mistakes:

• Adding files again instead of unstaging
• Committing without checking unstaged changes
• Using git checkout to stage files (wrong)

5. You modified two files: app.py and README.md. You staged app.py but not README.md. What will git status show?

hard

A. No changes to commit, working directory clean

B. Changes to be committed: app.py; Changes not staged for commit: README.md

C. Changes not staged for commit: app.py and README.md

D. Untracked files: app.py and README.md

Solution

1. Step 1: Identify staged and unstaged files

   app.py is staged, so it appears under "Changes to be committed".

2. Step 2: Identify unstaged files

   README.md is modified but not staged, so it appears under "Changes not staged for commit".

3. Final Answer:

   Changes to be committed: app.py; Changes not staged for commit: README.md -> Option B

4. Quick Check:

   Staged vs unstaged files shown separately [OK]

Hint: Staged files show as 'to be committed', unstaged as 'not staged' [OK]

Common Mistakes:

• Assuming all modified files are staged
• Confusing untracked with modified files
• Thinking working directory is clean with staged changes