Amending the last commit in Git - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to amend the last commit message.

Git

git commit --amend -m "[1]"

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

AUpdated commit message

Bgit status

Cgit push

Dgit log

Attempts:

3 left

💡 Hint

Common Mistakes

Using git push instead of git commit --amend.

Forgetting to put the message in quotes.

The git commit --amend -m command lets you change the last commit message.

2fill in blank

medium

Complete the command to amend the last commit without changing the message.

Git

git commit --amend [1]

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

A--reset-author

B--amend

C--no-edit

D--message

Attempts:

3 left

💡 Hint

Common Mistakes

Repeating --amend option unnecessarily.

Using --message when not changing the message.

The --no-edit option lets you amend the last commit without changing the message.

3fill in blank

hard

Fix the error in the command to amend the last commit message.

Git

git commit --amend -m [1]

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

A"Updated message"

BUpdated message"

C'Updated message'

DUpdated message

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting the message causes syntax errors.

Mismatched quotes cause errors.

The commit message must be inside quotes to be treated as a single string.

4fill in blank

hard

Fill both blanks to amend the last commit with a new message.

Git

git commit [1] [2] "Fix typo in README"

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

A--amend

B--no-edit

C--reset-author

D-m

Attempts:

3 left

💡 Hint

Common Mistakes

Using --no-edit with a new message.

Forgetting the -m flag for the message.

Use --amend to change the last commit and -m to provide a new message.

5fill in blank

hard

Fill all three blanks to amend the last commit with a new message and push force to origin.

Git

git commit [1] [2] "Add new feature" && git [3] origin main

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

A--amend

B-m

Cpush --force

D--reset-author

Attempts:

3 left

💡 Hint

Common Mistakes

Not using force push after amending a pushed commit.

Mixing up the order of options.

First, amend the commit with --amend, add the message with -m, then force push with push --force.

Practice

1. What does the git commit --amend command do?

easy

A. It modifies the last commit by changing its message or content.

B. It deletes the last commit permanently.

C. It creates a new commit without changing previous commits.

D. It resets the repository to the initial commit.

Solution

1. Step 1: Understand the purpose of git commit --amend

   This command is used to change the last commit, either by editing its message or adding new changes.

2. Step 2: Compare with other options

   Deleting commits or resetting the repository are different commands like git reset. Creating a new commit does not amend the last one.

3. Final Answer:

   It modifies the last commit by changing its message or content. -> Option A

4. Quick Check:

   Amend last commit = modify last commit [OK]

Hint: Amend changes last commit, not create or delete [OK]

Common Mistakes:

• Thinking it deletes the last commit
• Confusing amend with creating a new commit
• Assuming it resets the whole repo

2. Which of the following is the correct syntax to amend the last commit message in Git?

easy

A. git commit -amend "New message"

B. git amend commit -m "New message"

C. git commit --amend -m "New message"

D. git commit --edit-message "New message"

Solution

1. Step 1: Recall the correct syntax for amending commit message

   The correct command is git commit --amend -m "New message" to directly change the last commit message.

2. Step 2: Identify incorrect syntax

   Options B, C, and D use invalid flags or wrong order, which Git does not recognize.

3. Final Answer:

   git commit --amend -m "New message" -> Option C

4. Quick Check:

   Correct amend syntax = git commit --amend -m [OK]

Hint: Use --amend before -m to change message [OK]

Common Mistakes:

• Swapping order of flags
• Using non-existent flags like --edit-message
• Typing 'amend' as a separate command

3. Given the following commands executed in order:

echo "Hello" > file.txt
 git add file.txt
 git commit -m "Add file"
 echo "World" >> file.txt
 git add file.txt
 git commit --amend -m "Add file with content update"

What will git log -1 --pretty=%B output?

medium

A. Add file

B. Add file with content update

C. Add file
Add file with content update

D. No commit message

Solution

1. Step 1: Understand the commit history after commands

   First commit message is "Add file". Then file.txt is updated and staged. The git commit --amend replaces the last commit message with "Add file with content update".

2. Step 2: Check the latest commit message output

   The git log -1 --pretty=%B shows the last commit message, which is now "Add file with content update" after amend.

3. Final Answer:

   Add file with content update -> Option B

4. Quick Check:

   Amended commit message = updated message [OK]

Hint: Amend replaces last commit message and content [OK]

Common Mistakes:

• Thinking amend adds a new commit instead of replacing
• Expecting both messages to appear
• Assuming commit message stays unchanged

4. You ran git commit --amend but accidentally removed some changes from the last commit. How can you fix this?

medium

A. Delete the repository and clone again.

B. Run git commit --amend again without changes.

C. Use git push --force to overwrite remote.

D. Use git reflog to find the previous commit and reset to it.

Solution

1. Step 1: Understand the problem with amend

   Amending rewrites the last commit, so if changes were lost, the previous commit state is still in Git history.

2. Step 2: Use git reflog to recover

   git reflog shows recent commit states. You can find the commit before amend and reset to it to restore lost changes.

3. Final Answer:

   Use git reflog to find the previous commit and reset to it. -> Option D

4. Quick Check:

   Recover lost commit with reflog [OK]

Hint: Use reflog to recover lost commits after amend [OK]

Common Mistakes:

• Trying to fix by amending again without changes
• Deleting repo instead of recovering
• Forcing push without fixing local history

5. You committed a file with a typo in the message and forgot to add a new file. Which sequence correctly fixes both issues using amend?

hard

A. Add the new file, then run git commit --amend -m "Corrected message"

B. Run git commit --amend -m "Corrected message" first, then add the new file

C. Delete the last commit, add the new file, then commit again

D. Push the commit, then fix the message and add file in a new commit

Solution

1. Step 1: Stage the new file before amending

   To include the new file in the last commit, you must add it first with git add.

2. Step 2: Amend the commit with the corrected message

   Run git commit --amend -m "Corrected message" to update the commit message and include the staged new file.

3. Final Answer:

   Add the new file, then run git commit --amend -m "Corrected message" -> Option A

4. Quick Check:

   Stage files before amend to include them [OK]

Hint: Add files first, then amend commit message [OK]

Common Mistakes:

• Amending before adding new files
• Deleting commits unnecessarily
• Pushing before fixing local commit