git restore --staged to unstage - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to unstage a file named example.txt.

Git

git restore --staged [1]

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

A-m

Bexample.txt

C--all

D--help

Attempts:

3 left

💡 Hint

Common Mistakes

Using --all unstages all files, not just one.

Using -m is for commit messages, not unstaging.

Using --help shows help, not unstaging.

The command git restore --staged example.txt unstages the file named example.txt from the staging area.

2fill in blank

medium

Complete the command to unstage all files at once.

Git

git restore --staged [1]

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

A--all

Bexample.txt

C--cached

D-p

Attempts:

3 left

💡 Hint

Common Mistakes

Using --cached is not valid with git restore.

Using -p is for patch mode, not unstaging all files.

Specifying a single file unstages only that file.

Using git restore --staged --all unstages all files currently staged for commit.

3fill in blank

hard

Fix the error in the command to unstage a file named index.html.

Git

git restore --staged [1]

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

Aindex_html

Bindex.html/

C--index.html

Dindex.html

Attempts:

3 left

💡 Hint

Common Mistakes

Adding a slash after the file name causes an error.

Using dashes before the file name is invalid.

Changing underscores changes the file name.

The correct syntax is to provide the exact file name without extra slashes or dashes: index.html.

4fill in blank

hard

Fill both blanks to unstage the file style.css and show the status afterward.

Git

git restore --staged [1] && git [2]

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

Astyle.css

Bstatus

Clog

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Using git log instead of git status does not show staged files.

Using git commit tries to commit instead of showing status.

Not specifying the file unstages nothing.

The command unstages style.css and then shows the current git status with git status.

5fill in blank

hard

Fill all three blanks to unstage app.js, add README.md to staging, and then check the status.

Git

git restore --staged [1] && git add [2] && git [3]

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

Aapp.js

BREADME.md

Cstatus

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up file names in the wrong commands.

Using git commit instead of git status at the end.

Forgetting to unstage or add files properly.

This sequence unstages app.js, stages README.md, and then shows the current status.

Practice

1. What does the command git restore --staged <file> do in Git?

easy

A. It commits the file to the repository.

B. It deletes the file from the working directory and staging area.

C. It removes the file from the staging area but keeps the changes in the working directory.

D. It discards all changes in the file and restores it to the last commit.

Solution

1. Step 1: Understand the staging area role

   The staging area holds files ready to be committed, but changes still exist in the working directory.

2. Step 2: Effect of git restore --staged

   This command removes the file from staging but keeps your edits in the working directory, so you can fix or adjust before committing.

3. Final Answer:

   It removes the file from the staging area but keeps the changes in the working directory. -> Option C

4. Quick Check:

   Unstage = remove from staging, keep edits [OK]

Hint: Unstage means remove from staging, keep your edits [OK]

Common Mistakes:

• Thinking it deletes the file from disk
• Confusing it with discarding changes
• Assuming it commits the file immediately

2. Which of the following is the correct syntax to unstage a file named app.js using git restore?

easy

A. git restore --staged app.js

B. git restore app.js --staged

C. git restore --unstage app.js

D. git restore --remove app.js

Solution

1. Step 1: Recall correct option order for flags

   In Git commands, flags usually come before the file names.

2. Step 2: Apply to git restore --staged

   The correct syntax places --staged before the file name: git restore --staged app.js.

3. Final Answer:

   git restore --staged app.js -> Option A

4. Quick Check:

   Flags before files = correct syntax [OK]

Hint: Put flags before filenames in git commands [OK]

Common Mistakes:

• Placing --staged after the filename
• Using non-existent flags like --unstage
• Confusing restore with reset commands

3. Given the following sequence of commands:

echo 'initial' > file.txt
 git add file.txt
 git commit -m 'initial'
 echo 'Hello' > file.txt
 git add file.txt
 git restore --staged file.txt
 git status

What will git status show about file.txt?

medium

A. file.txt is staged for commit.

B. file.txt is deleted.

C. file.txt is unmodified and not staged.

D. file.txt is modified but not staged.

Solution

1. Step 1: Analyze the commands step-by-step

   First, 'Hello' is written to file.txt. Then, git add stages it. Next, git restore --staged file.txt removes it from staging but keeps the change.

2. Step 2: Understand the status after unstaging

   Since the file is modified but unstaged, git status will show it as modified but not staged for commit.

3. Final Answer:

   file.txt is modified but not staged. -> Option D

4. Quick Check:

   Unstaged changes = modified but not staged [OK]

Hint: Unstaged files show as modified but not staged [OK]

Common Mistakes:

• Assuming file is still staged after restore --staged
• Thinking file is unmodified after unstaging
• Confusing unstaged with deleted

4. You ran git restore --staged myfile.txt but got an error: error: pathspec 'myfile.txt' did not match any files. What is the most likely cause?

medium

A. The file myfile.txt is not currently staged.

B. You misspelled the command; it should be git reset --staged.

C. The file does not exist in the working directory.

D. You need to add --force to the command.

Solution

1. Step 1: Understand the error message meaning

   The error says the file path does not match any staged files, meaning Git can't find it in the staging area.

2. Step 2: Check the file's staging status

   If the file is not staged, git restore --staged cannot unstage it, causing this error.

3. Final Answer:

   The file myfile.txt is not currently staged. -> Option A

4. Quick Check:

   Unstage error means file not staged [OK]

Hint: File must be staged to unstage it [OK]

Common Mistakes:

• Assuming command syntax is wrong
• Thinking file must exist only in working directory
• Trying to force unstage without staging first

5. You staged two files, index.html and style.css, but realize you only want to commit index.html. Which command correctly unstages style.css without losing your edits?

hard

A. git checkout -- style.css

B. git restore --staged style.css

C. git reset --hard style.css

D. git rm --cached style.css

Solution

1. Step 1: Identify the goal

   You want to unstage style.css but keep your changes in the working directory.

2. Step 2: Compare commands

   git restore --staged style.css unstages the file but keeps edits.
   git reset --hard style.css is invalid syntax with paths and cannot unstage a specific file.
   git checkout -- style.css updates working tree from index but does not unstage.
   git rm --cached style.css stages a deletion, which is not desired.

3. Final Answer:

   git restore --staged style.css -> Option B

4. Quick Check:

   Use restore --staged to unstage safely [OK]

Hint: Use git restore --staged to unstage without losing edits [OK]

Common Mistakes:

• Using git checkout which discards changes
• Using git rm --cached which removes file tracking
• Confusing git reset with discard commands