Why staging before committing matters in Git - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use staging area before commit?

What is the main purpose of the staging area in Git before committing changes?

A To merge branches before committing

B To permanently delete unwanted files from the repository

C To selectively choose which changes to include in the next commit

D To automatically push changes to the remote repository

💡 Hint

Think about how you prepare a photo album by picking only some pictures before printing.

The staging area lets you pick exactly which changes to save in your next commit. This helps keep commits clean and focused.

💻 Command Output

intermediate

Output of git status after staging

What will git status show after you run git add file.txt but before committing?

Git

git add file.txt
git status

A Changes to be committed: new file: file.txt

B Untracked files: file.txt

C Nothing to commit, working tree clean

D Changes not staged for commit: modified: file.txt

💡 Hint

After adding, the file is ready to be saved in the next commit.

Running git add moves changes to the staging area, so git status shows them as ready to commit.

🔀 Workflow

advanced

Correct sequence to stage and commit changes

Which sequence of commands correctly stages and commits a file named app.py with a message 'Add app script'?

A

git commit -m 'Add app script' app.py
git add app.py

B

git add app.py
git commit -m 'Add app script'

C

git commit app.py
git add -m 'Add app script'

D

git add -m 'Add app script' app.py
git commit

💡 Hint

Remember: add first, then commit with message.

You must stage files with git add before committing. The commit command includes the message.

❓ Troubleshoot

advanced

Why commit does not include recent changes?

You modified index.html but after running git commit -m 'Update', the changes are not saved in the commit. What is the likely reason?

A You forgot to stage the changes with <code>git add index.html</code>

B The commit message is too short

C The file is ignored by .gitignore

D You need to push before committing

💡 Hint

Think about how you must tell Git which changes to save.

Git only commits changes that have been staged. If you skip git add, the commit won't include your edits.

✅ Best Practice

expert

Why commit small, focused changes after staging?

What is the main benefit of staging and committing small, focused changes instead of one big commit?

A It reduces the size of the repository on disk

B It speeds up pushing to the remote repository

C It automatically merges branches without conflicts

D It makes it easier to review, understand, and revert specific changes later

💡 Hint

Think about how organizing photos by event helps find them later.

Small commits help teams review code clearly and fix problems by undoing specific changes without affecting others.