Amending the last commit in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of amending last commit with new message

What is the output of the following command sequence in a git repository?

git commit --amend -m "Updated commit message"

Git

git commit --amend -m "Updated commit message"

A Successfully amended the last commit with the new message.

B Error: You have uncommitted changes. Commit aborted.

C fatal: no changes added to commit (use "git add" and/or "git commit -a")

D Error: No previous commit to amend.

💡 Hint

Amending changes the last commit message or content if staged.

The command replaces the last commit message with the new one if there are no conflicts or errors.

🧠 Conceptual

intermediate

Effect of amending last commit on commit hash

What happens to the commit hash when you amend the last commit in git?

A The commit hash changes only if files are added, not if message changes.

B The commit hash stays the same because only the message changes.

C The commit hash changes because the commit content or metadata changes.

D The commit hash stays the same if the commit is pushed already.

💡 Hint

Commit hash depends on commit content and metadata.

Amending changes the commit content or metadata, so git creates a new commit with a new hash.

❓ Troubleshoot

advanced

Error when amending last commit with unstaged changes

You run git commit --amend but get the error:

fatal: no changes added to commit (use "git add" and/or "git commit -a")

What is the cause?

A You have unstaged changes; git cannot amend without staged changes.

B Your git repository is corrupted.

C You are trying to amend a pushed commit without force push.

D You have no previous commit to amend.

💡 Hint

Amend requires staged changes or message edit.

Git requires changes to be staged to include them in the amended commit; otherwise, it errors.

🔀 Workflow

advanced

Correct workflow to amend last commit with new file added

Which sequence correctly amends the last commit by adding a new file notes.txt?

A touch notes.txt<br>git commit --amend --amend

B touch notes.txt<br>git add notes.txt<br>git commit --amend --no-edit

C git add notes.txt<br>git commit -m "Add notes"<br>git commit --amend

D touch notes.txt<br>git commit --amend -m "Add notes"<br>git add notes.txt

💡 Hint

You must stage changes before amending.

First create the file, stage it, then amend the last commit without changing the message.

✅ Best Practice

expert

Best practice when amending a commit already pushed to shared repository

You amended your last commit after pushing it to a shared repository. What is the best practice to avoid problems for others?

A Ask all collaborators to reset their branches before you push.

B Force push the amended commit immediately to update the remote branch.

C Delete the remote branch and push the amended commit as new branch.

D Avoid amending pushed commits; instead, create a new commit to fix issues.

💡 Hint

Rewriting history after pushing can cause conflicts for others.

Amending pushed commits rewrites history and can confuse collaborators; better to add new commits.