Working directory state in Git - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to check the current status of your working directory.

Git

git [1]

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

Astatus

Bpush

Cclone

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git commit' instead of 'git status' to check changes.

Using 'git push' which sends changes to remote, not shows status.

The git status command shows the current state of the working directory and staging area.

2fill in blank

medium

Complete the command to discard changes in a file named app.py and restore it to the last committed state.

Git

git checkout -- [1]

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

Aconfig.yaml

BREADME.md

Cindex.html

Dapp.py

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong file name that does not exist.

Omitting the double dash -- which separates options from file names.

The command git checkout -- app.py restores app.py to the last committed version, discarding local changes.

3fill in blank

hard

Fix the error in the command to stage all changed files for commit.

Git

git [1] .

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

Acommit

Bpush

Cadd

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git commit .' which tries to commit without staging.

Using 'git push .' which is invalid syntax.

The command git add . stages all changes in the current directory for the next commit.

4fill in blank

hard

Complete the command to switch to the branch named feature.

Git

git [1] [2]

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

Acheckout

Bbranch

Cfeature

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git branch feature' only creates but does not switch.

Using 'git commit feature' which is invalid.

The command git checkout feature switches to the branch named feature.

5fill in blank

hard

Fill all three blanks to show the differences between the working directory and the last commit for the file server.js.

Git

git [1] [2] [3]

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

Adiff

B--

Cserver.js

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'git status server.js' which shows status but not detailed differences.

Omitting the double dash which can confuse git about arguments.

The command git diff -- server.js shows changes in server.js that are not yet staged.

Practice

1. What does the git status command show you about your working directory?

easy

A. It shows which files are new, modified, or staged for commit.

B. It deletes all untracked files from the directory.

C. It permanently commits all changes to the repository.

D. It resets the repository to the last commit.

Solution

1. Step 1: Understand the purpose of git status

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

2. Step 2: Identify what git status reports

   It lists new files, modified files, and files staged for commit, helping you track changes.

3. Final Answer:

   It shows which files are new, modified, or staged for commit. -> Option A

4. Quick Check:

   Working directory changes = git status output [OK]

Hint: Remember: git status shows current file changes and staging [OK]

Common Mistakes:

• Confusing git status with git commit
• Thinking git status deletes files
• Assuming git status changes files automatically

2. Which of the following commands correctly stages a file named app.js for commit?

easy

A. git commit app.js

B. git status app.js

C. git add app.js

D. git push app.js

Solution

1. Step 1: Identify the command to stage files

   The git add command is used to add files to the staging area.

2. Step 2: Confirm the correct syntax for staging a specific file

   Using git add app.js stages the file named app.js for the next commit.

3. Final Answer:

   git add app.js -> Option C

4. Quick Check:

   Stage files = git add [OK]

Hint: Use git add to stage files before committing [OK]

Common Mistakes:

• Using git commit to stage files
• Trying to use git status to stage
• Using git push before commit

3. Given the following sequence of commands, what will git status show about index.html?

echo 'Hello' > index.html
git add index.html
echo 'World' >> index.html
git status

medium

A. index.html is staged and has unstaged changes.

B. index.html is deleted.

C. index.html is untracked.

D. index.html is staged and unchanged.

Solution

1. Step 1: Analyze the commands on index.html

   First, 'Hello' is written and the file is staged with git add. Then 'World' is appended, modifying the file after staging.

2. Step 2: Understand git status output

   Git will show index.html as staged (with 'Hello') but also as modified (unstaged changes with 'World').

3. Final Answer:

   index.html is staged and has unstaged changes. -> Option A

4. Quick Check:

   Modified after staging = staged + unstaged changes [OK]

Hint: Changes after git add show as unstaged modifications [OK]

Common Mistakes:

• Assuming staging updates automatically after file change
• Thinking file is untracked after git add
• Confusing staged with committed

4. You ran git add README.md but git status still shows README.md under 'Changes not staged for commit'. What is the likely cause?

medium

A. README.md is ignored by .gitignore.

B. You modified README.md after running git add.

C. You committed README.md already.

D. README.md is deleted from the working directory.

Solution

1. Step 1: Understand git add and file modification

   Running git add stages the current file state. If the file changes after, those changes are unstaged.

2. Step 2: Interpret git status showing unstaged changes

   If README.md appears under 'Changes not staged for commit', it means it was modified after staging.

3. Final Answer:

   You modified README.md after running git add. -> Option B

4. Quick Check:

   Modify after add = unstaged changes shown [OK]

Hint: Modify after git add causes unstaged changes [OK]

Common Mistakes:

• Assuming git add stages future changes automatically
• Thinking .gitignore affects already tracked files
• Confusing committed files with staged files

5. You want to prepare a commit but accidentally staged a large file secret.txt. How can you remove it from the staging area without deleting the file from your working directory?

hard

A. git checkout secret.txt

B. git rm secret.txt

C. git clean secret.txt

D. git reset secret.txt

Solution

1. Step 1: Understand the difference between unstaging and deleting

   To remove a file from staging but keep it in the working directory, you must unstage it.

2. Step 2: Identify the correct command to unstage a file

   git reset secret.txt removes the file from the staging area without deleting it from disk.

3. Final Answer:

   git reset secret.txt -> Option D

4. Quick Check:

   Unstage file = git reset filename [OK]

Hint: Use git reset to unstage files without deleting [OK]

Common Mistakes:

• Using git rm deletes the file from disk
• Using git checkout resets file content, not staging
• Using git clean deletes untracked files