Git mental model (snapshots not diffs) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to create a new commit snapshot in Git.

Git

git commit -m [1]

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

A-a

B"Initial commit"

Cpush

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'push' instead of a message

Omitting the message quotes

The git commit -m command creates a new snapshot with a message describing the changes.

2fill in blank

medium

Complete the command to see the current snapshot history in Git.

Git

git [1]

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

Abranch

Bclone

Cadd

Dlog

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'add' which stages files

Using 'branch' which manages branches

The git log command shows the list of snapshots (commits) made so far.

3fill in blank

hard

Fix the error in the command to save all changes as a snapshot.

Git

git [1] -m "Save all changes"

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

Acommit

Bstatus

Cpush

Dcheckout

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'push' which sends commits to remote

Using 'status' which shows current state

The git commit command saves the current staged changes as a snapshot with a message.

4fill in blank

hard

Fill both blanks to create a snapshot after adding files.

Git

git [1] . && git [2] -m "Snapshot after adding files"

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

Aadd

Bcommit

Cpush

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'push' instead of 'commit'

Skipping 'add' before commit

First, git add . stages all changes, then git commit -m creates the snapshot.

5fill in blank

hard

Fill all three blanks to create a snapshot and send it to the remote repository.

Git

git [1] . && git [2] -m "Update snapshot" && git [3] origin main

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

Aadd

Bcommit

Cpush

Dfetch

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'fetch' instead of 'push'

Committing before adding files

Stage changes with add, save snapshot with commit, then send it to remote with push.

Practice

1. What does Git save when you run git commit?

easy

A. A backup copy of your entire computer

B. Only the changes made since the last commit

C. A list of all commands you typed

D. A snapshot of all your files at that moment

Solution

1. Step 1: Understand what git commit does

   It records the current state of your project files as a snapshot.

2. Step 2: Differentiate snapshot from changes

   Unlike some systems, Git saves the whole snapshot, not just the changes.

3. Final Answer:

   A snapshot of all your files at that moment -> Option D

4. Quick Check:

   Git saves snapshots, not diffs [OK]

Hint: Remember: Git snapshots whole files, not just changes [OK]

Common Mistakes:

• Thinking Git saves only changes (diffs)
• Confusing commit with backup
• Believing commit saves command history

2. Which of the following is the correct command to create a snapshot in Git?

easy

A. git snapshot

B. git save

C. git commit

D. git backup

Solution

1. Step 1: Recall Git commands for saving work

   The command to save a snapshot is git commit.

2. Step 2: Verify other options

   Commands like git snapshot, git save, and git backup do not exist in Git.

3. Final Answer:

   git commit -> Option C

4. Quick Check:

   git commit creates snapshots [OK]

Hint: Use git commit to save snapshots [OK]

Common Mistakes:

• Using non-existent commands like git save
• Confusing commit with backup commands
• Trying git snapshot which is invalid

3. Given this sequence of commands:

echo "Hello" > file.txt
git add file.txt
git commit -m "First snapshot"
echo "World" >> file.txt
git add file.txt
git commit -m "Second snapshot"

What does the second commit snapshot contain?

medium

A. Only the line "World" added to file.txt

B. The entire file.txt with both "Hello" and "World" lines

C. Only the line "Hello" in file.txt

D. An empty file.txt

Solution

1. Step 1: Understand what each commit saves

   Each commit saves a full snapshot of the file at that time, not just changes.

2. Step 2: Analyze the second commit content

   After appending "World", the second commit snapshot includes both "Hello" and "World" lines in file.txt.

3. Final Answer:

   The entire file.txt with both "Hello" and "World" lines -> Option B

4. Quick Check:

   Git snapshots save full file content [OK]

Hint: Each commit saves full file content, not just added lines [OK]

Common Mistakes:

• Thinking commit saves only new lines
• Confusing snapshots with diffs
• Assuming commit saves partial file

4. You ran git commit but Git says "nothing to commit, working tree clean". What is the most likely reason?

medium

A. There are no changes since the last snapshot

B. You forgot to add files with git add before commit

C. Your Git repository is corrupted

D. You need to restart your computer

Solution

1. Step 1: Understand the message meaning

   "Nothing to commit, working tree clean" means no changes are detected compared to last commit.

2. Step 2: Check if files were changed

   If no files changed, Git has no new snapshot to save, so commit does nothing.

3. Final Answer:

   There are no changes since the last snapshot -> Option A

4. Quick Check:

   No changes = no new snapshot [OK]

Hint: No changes means no new commit possible [OK]

Common Mistakes:

• Assuming you must always run git add before commit even if no changes
• Thinking repository is corrupted
• Restarting computer unnecessarily

5. You want to save your project state but only some files changed. How does Git store this when you run git commit?

hard

A. Git saves a full snapshot of all files, but reuses unchanged files from previous commits internally

B. Git saves only the changed files as diffs

C. Git saves only the changed files as full copies

D. Git saves nothing until you run git push

Solution

1. Step 1: Recall Git snapshot model

   Git saves a full snapshot of the project at commit time, not just diffs.

2. Step 2: Understand Git's storage optimization

   Internally, Git reuses unchanged files from previous commits to save space efficiently.

3. Final Answer:

   Git saves a full snapshot of all files, but reuses unchanged files from previous commits internally -> Option A

4. Quick Check:

   Snapshots with internal reuse = Git saves a full snapshot of all files, but reuses unchanged files from previous commits internally [OK]

Hint: Git snapshots all files but stores unchanged ones efficiently [OK]

Common Mistakes:

• Thinking Git saves only diffs
• Believing commit saves nothing until push
• Assuming changed files are saved as full copies only