Difference between reset and revert in Git - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to undo the last commit but keep changes staged.

Git

git [1] --soft HEAD~1

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

Acheckout

Breset

Ccommit

Drevert

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'revert' instead of 'reset' for undoing commits locally.

The git reset --soft HEAD~1 command moves the branch pointer back by one commit but keeps the changes staged.

2fill in blank

medium

Complete the command to create a new commit that undoes changes from a specific commit.

Git

git [1] <commit-hash>

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

Areset

Bmerge

Ccheckout

Drevert

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'reset' which rewrites history and can cause issues in shared branches.

The git revert command creates a new commit that reverses the changes made by the specified commit.

3fill in blank

hard

Fix the error in the command to undo the last commit and discard changes in working directory.

Git

git [1] --hard HEAD~1

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

Areset

Brevert

Ccommit

Dstash

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'revert' which does not discard working directory changes.

The git reset --hard HEAD~1 command moves the branch pointer back and discards all changes in the working directory.

4fill in blank

hard

Fill both blanks to create a new commit that undoes the last commit and pushes it to remote.

Git

git [1] HEAD~1 && git [2] origin main

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

Arevert

Breset

Cpush

Dfetch

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'reset' before push which rewrites history and can cause conflicts.

First, git revert HEAD~1 creates a new commit undoing the last commit. Then, git push origin main sends the changes to the remote repository.

5fill in blank

hard

Fill both blanks to reset the branch to the previous commit and force push to remote.

Git

git [1] --hard HEAD~1 && git [2] origin main --force

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

Areset

Brevert

Cpush

Dfetch

Attempts:

3 left

💡 Hint

Common Mistakes

Using revert instead of reset for history rewrite.

Forgetting --force when pushing after reset.

git reset --hard HEAD~1 moves the branch pointer back one commit and discards changes. Then git push origin main --force updates the remote branch forcibly.