Untracked vs tracked files in Git - CLI Comparison

Introduction

When you work with Git, files in your project can be either tracked or untracked. Tracked files are those Git knows about and monitors for changes. Untracked files are new files Git has not started tracking yet. Understanding this helps you control what changes get saved in your project history.

When you create a new file and want to add it to your project history.

When you want to see which files are new and not yet added to Git.

When you want to ignore certain files so Git does not track them.

When you want to check if your changes are ready to be saved.

When you want to clean up files that are not part of your project.

Commands

This command shows the current state of your project, listing tracked files with changes and untracked files that Git does not know yet.

Terminal

git status

Expected Output

On branch main



No commits yet



Untracked files:

  (use "git add <file>..." to include in what will be committed)



	newfile.txt



nothing added to commit but untracked files present (use "git add" to track)

This command tells Git to start tracking the new file by adding it to the staging area, preparing it to be saved in the next commit.

Terminal

git add newfile.txt

Expected Output

No output (command runs silently)

Run again to see that the file is now tracked and staged for commit.

Terminal

git status

Expected Output

On branch main



No commits yet



Changes to be committed:

  (use "git rm --cached <file>..." to unstage)



	new file:   newfile.txt

This command saves the staged changes (including the new tracked file) into the project history with a message describing the change.

Terminal

git commit -m "Add newfile.txt"

Expected Output

[main (root-commit) abcdef1] Add newfile.txt

 1 file changed, 0 insertions(+), 0 deletions(-)

 create mode 100644 newfile.txt

→

-m - Add a commit message inline

Check the status again to confirm there are no untracked or unstaged changes left.

Terminal

git status

Expected Output

On branch main



nothing to commit, working tree clean

Key Concept

If you remember nothing else from this pattern, remember: untracked files are new files Git does not monitor until you add them, and tracked files are those Git watches for changes.

Common Mistakes

Trying to commit a new file without adding it first

Git will not include untracked files in commits unless they are added to the staging area.

Use 'git add filename' to start tracking the file before committing.

Ignoring untracked files that should be part of the project

Important new files will not be saved in the project history and can be lost.

Regularly check 'git status' and add new files you want to keep.

Adding files that should be ignored (like logs or temp files)

This clutters the project history with unnecessary files.

Use a .gitignore file to tell Git which files to ignore.

Summary

Use 'git status' to see which files are tracked and untracked.

Add new files with 'git add filename' to start tracking them.

Commit tracked changes with 'git commit -m "message"' to save them.

Practice

1. What does it mean when a file is untracked in Git?

easy

A. The file is already included in the last commit.

B. Git does not know about the file yet and it is not included in commits.

C. The file is ignored by Git due to .gitignore rules.

D. The file is staged and ready to be committed.

Solution

1. Step 1: Understand the meaning of untracked files

   Untracked files are those that Git has not seen before and are not part of any commit.

2. Step 2: Compare with tracked files

   Tracked files are known to Git and included in commits, unlike untracked files.

3. Final Answer:

   Git does not know about the file yet and it is not included in commits. -> Option B

4. Quick Check:

   Untracked = Not known to Git [OK]

Hint: Untracked means Git hasn't seen the file yet [OK]

Common Mistakes:

• Confusing untracked with ignored files
• Thinking untracked files are staged
• Assuming untracked files are committed

2. Which Git command is used to start tracking an untracked file?

easy

A. git commit

B. git status

C. git push

D. git add

Solution

1. Step 1: Identify the command to track files

   The git add command tells Git to start tracking a file by adding it to the staging area.

2. Step 2: Differentiate from other commands

   git commit saves changes, git push sends commits to remote, and git status shows file states.

3. Final Answer:

   git add -> Option D

4. Quick Check:

   Start tracking = git add [OK]

Hint: Use git add to track new files [OK]

Common Mistakes:

• Using git commit before adding files
• Confusing git push with tracking
• Thinking git status tracks files

3. Given the following Git status output:

Untracked files:
  (use "git add <file>..." to include in what will be committed)
    newfile.txt

Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)
    modified: trackedfile.txt

Which files are currently tracked by Git?

medium

A. trackedfile.txt only

B. Both newfile.txt and trackedfile.txt

C. newfile.txt only

D. Neither file is tracked

Solution

1. Step 1: Analyze the status output sections

   The "Untracked files" section lists files Git does not track yet, here newfile.txt. The "Changes to be committed" section lists tracked files staged for commit, here trackedfile.txt.

2. Step 2: Determine tracked files

   Only trackedfile.txt is tracked because it is staged. newfile.txt is untracked.

3. Final Answer:

   trackedfile.txt only -> Option A

4. Quick Check:

   Tracked files = staged or committed files [OK]

Hint: Tracked files appear under 'Changes to be committed' [OK]

Common Mistakes:

• Assuming untracked files are tracked
• Confusing staged with untracked
• Ignoring the status section labels

4. You ran git add newfile.txt but git status still shows newfile.txt as untracked. What is the most likely reason?

medium

A. The file is listed in .gitignore and ignored by Git.

B. You forgot to commit after adding the file.

C. You used the wrong filename in the add command.

D. Git does not track files with certain extensions.

Solution

1. Step 1: Understand why git add might not track a file

   If a file is ignored by Git due to .gitignore rules, git add will not track it and it remains untracked.

2. Step 2: Eliminate other reasons

   Committing is not required to track a file; wrong filename would cause an error; Git tracks all extensions unless ignored.

3. Final Answer:

   The file is listed in .gitignore and ignored by Git. -> Option A

4. Quick Check:

   Ignored files stay untracked despite git add [OK]

Hint: Check .gitignore if git add doesn't track file [OK]

Common Mistakes:

• Thinking commit is needed to track
• Ignoring .gitignore rules
• Assuming Git restricts file types

5. You have a folder with files: file1.txt (tracked, modified), file2.txt (untracked), and file3.log (untracked). Your .gitignore contains *.log. You want to commit file2.txt but not the changes in file1.txt or file3.log. What is the correct sequence of commands?

hard

A. git add file3.log; git commit -m "Add file3"

B. git add .; git commit -m "Add all files"

C. git add file2.txt; git commit -m "Add file2"

D. git commit -a -m "Add file2 and file3"

Solution

1. Step 1: Understand .gitignore effect

   The pattern *.log in .gitignore causes file3.log to be ignored and untracked, so it won't be added by git add ..

2. Step 2: Choose commands to add only file2.txt

   Using git add file2.txt adds only that file without staging changes to tracked file1.txt. Then commit saves it. git add file3.log is ignored. git add . would add file2.txt AND stage changes to file1.txt. Using git commit -a only commits tracked files, so untracked file2.txt won't be included.

3. Final Answer:

   git add file2.txt; git commit -m "Add file2" -> Option C

4. Quick Check:

   Use git add on untracked file, ignore .log files [OK]

Hint: Add untracked files explicitly; .gitignore blocks others [OK]

Common Mistakes:

• Using git commit -a to add untracked files
• Adding ignored files by mistake
• Using git add . which also stages changes to tracked files