Untracked vs tracked files in Git - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to see untracked files in your Git repository.

Git

git status [1]

Drag options to blanks, or click blank then click option'

A--untracked-files=no

B--untracked-files=all

C--tracked-files=all

D--show-untracked

Attempts:

3 left

💡 Hint

Common Mistakes

Using --untracked-files=no hides untracked files.

Using --tracked-files=all is not a valid option.

Using --show-untracked is not a git status option.

The git status --untracked-files=all command shows all untracked files in the repository.

2fill in blank

medium

Complete the command to add a new file to the tracked files in Git.

Git

git [1] newfile.txt

Drag options to blanks, or click blank then click option'

Acommit

Bpush

Cadd

Dtrack

Attempts:

3 left

💡 Hint

Common Mistakes

Using git commit before adding files.

Using git push to add files.

Using git track which is not a git command.

The git add command stages new files to be tracked by Git.

3fill in blank

hard

Fix the error in the command to remove a file from tracking but keep it locally.

Git

git [1] --cached file.txt

Drag options to blanks, or click blank then click option'

Arm

Breset

Cuntrack

Dremove

Attempts:

3 left

💡 Hint

Common Mistakes

Using git reset which resets commits, not files.

Using git remove which is not a git command.

Using git untrack which does not exist.

The git rm --cached command removes a file from tracking but leaves it in your local folder.

4fill in blank

hard

Fill both blanks to create a command that shows tracked files and ignores untracked files.

Git

git status [1]=[2]

Drag options to blanks, or click blank then click option'

A--untracked-files

Bno

Call

Dtracked

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'all' to show untracked files instead of hiding them.

Using 'tracked' which is not a valid option.

The command git status --untracked-files=no shows only tracked files and hides untracked files.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps tracked files to their sizes if size is greater than 1000 bytes.

Git

file_sizes = [1]: os.path.getsize([2]) for [3] in tracked_files if os.path.getsize([3]) > 1000

Drag options to blanks, or click blank then click option'

Af

Attempts:

3 left

💡 Hint

Common Mistakes

Using different variable names causing errors.

Using undefined variables.

Using f as the variable name for files in the comprehension is standard and consistent.

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