git restore --staged to unstage - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of unstaging a file with git restore --staged?

You have staged a file named example.txt. You run git restore --staged example.txt. What happens to the file's state?

A The file is committed automatically.

B The file is deleted from the working directory and staging area.

C The file is staged again with no changes.

D The file is removed from the staging area but changes remain in the working directory.

💡 Hint

Think about what 'unstaging' means in Git.

Using git restore --staged removes the file from the staging area (index) but keeps your changes in the working directory. It does not delete or commit the file.

🧠 Conceptual

intermediate

Which command correctly unstages a file in Git?

You accidentally staged a file named config.yaml. Which command will unstage it without losing your changes?

A git restore --staged config.yaml

B git rm --cached config.yaml

C git commit --amend config.yaml

D git reset --hard config.yaml

💡 Hint

Unstaging means removing from the index but keeping the file.

git restore --staged removes the file from staging but keeps changes. git reset --hard discards changes. git commit --amend changes commits. git rm --cached removes the file from staging but keeps it in the working directory.

❓ Troubleshoot

advanced

Why does git restore --staged not remove changes from the working directory?

You ran git restore --staged README.md but your changes in the file are still visible. Why?

A Because <code>git restore --staged</code> only removes the file from the staging area, not the working directory.

B Because the file is locked by another process.

C Because the command requires the <code>--worktree</code> option to remove changes.

D Because the file was never staged to begin with.

💡 Hint

Think about the difference between staging area and working directory.

git restore --staged unstages the file but does not touch your actual file changes in the working directory. To discard changes, a different command is needed.

🔀 Workflow

advanced

What is the correct sequence to unstage a file and then discard its changes?

You staged and modified app.js. You want to unstage it and also remove all changes, restoring it to the last commit. Which sequence is correct?

A git reset HEAD app.js; git rm app.js

B git restore app.js; git restore --staged app.js

C git restore --staged app.js; git restore app.js

D git commit --amend; git restore app.js

💡 Hint

First remove from staging, then discard changes.

First, git restore --staged app.js unstages the file. Then, git restore app.js discards changes in the working directory, restoring the last committed version.

✅ Best Practice

expert

Which command safely unstages all files without discarding any changes?

You have multiple files staged but want to unstage all of them at once without losing any work. Which command should you use?

A git reset --hard

B git restore --staged .

C git clean -fd

D git rm --cached -r .

💡 Hint

Unstage all files but keep changes intact.

git restore --staged . unstages all files in the current directory and below, keeping your changes. git reset --hard discards all changes. git clean -fd removes untracked files. git rm --cached -r . removes files from staging but keeps them in the working directory.