git add for staging files - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of staging a single file?

You run the command git add README.md in a repository. What is the immediate output shown by Git?

A No output is shown; the file is staged silently.

B Output: 'README.md added to staging area'

C Output: 'Changes to be committed:' followed by the file name

D Output: 'Error: file not found'

💡 Hint

Think about what Git normally shows when you add files.

By default, git add does not produce any output when it stages files successfully. It silently updates the staging area.

💻 Command Output

intermediate

What happens when you stage all files with a wildcard?

You run git add *.txt in a directory with files: notes.txt, todo.txt, and image.png. What files get staged?

A Only notes.txt and todo.txt are staged.

B No files are staged; wildcard is not supported.

C Only image.png is staged.

D All files including image.png are staged.

💡 Hint

Consider how shell wildcards work before Git sees the command.

The shell expands *.txt to all files ending with .txt before Git runs. So only notes.txt and todo.txt are staged.

❓ Configuration

advanced

Which command stages all modified and deleted files but not new untracked files?

You want to stage all changes except new untracked files. Which command achieves this?

A git add -A

B git add -u

C git add .

D git add --all

💡 Hint

Look at the difference between -u and -A options.

git add -u stages modified and deleted files but ignores new untracked files. git add -A and git add --all stage all changes including new files.

❓ Troubleshoot

advanced

Why does git add fail with 'fatal: pathspec ... did not match any files'?

You run git add docs/*.md but get the error: 'fatal: pathspec 'docs/*.md' did not match any files'. What is the most likely cause?

A The docs directory is not tracked by Git.

B Git does not support wildcards in <code>git add</code>.

C There are no .md files in the docs directory.

D You need to run <code>git init</code> first.

💡 Hint

Check if the files actually exist in the specified path.

The error means the shell did not expand the wildcard because no matching files exist. Git received the literal pattern and could not find files matching it.

✅ Best Practice

expert

Which command safely stages only parts of a file interactively?

You want to stage only some changes inside a file, not the whole file. Which command lets you do this interactively?

A git add --force filename

B git add --all filename

C git add -u filename

D git add -p filename

💡 Hint

Look for the option that allows patch mode.

git add -p lets you review changes chunk by chunk and choose which to stage. Other options stage whole files or all changes.