Gitopedia Blog Git Course in VS CodeGit Course

Previous step Next step

4. Resetting unwanted changes

Conclusion and next steps

Congratulations! Now you are a master of resetting unwanted changes in Git! You've learned how to compare your working tree with the repository, how to discard local and staged changes, and how to amend the last commit to include last-minute fixes.

Up next, we'll explore tagging and branching, crucial skills for managing different versions and features within your project. But before we move on...

Quiz time!

Quiz yourself

1/7: What does the command git status do?

Commits your changes to the repository

Pushes your changes to a remote repository

Shows the current state of your working tree and staging area

Reverts your project to the last committed state

Prints the latest IT news

2/7: How do you check the differences between your working tree and the last commit?

git

git diff

git status

git log

3/7: In what scenarios would you use the git diff command?

To see what changed in the working tree compared to the last commit

To compare the contents of a file between two commits

To see the difference between two branches

All of the above

4/7: What does the command git restore . do?

Stages all changes in the current directory

Restores all files in the current directory to their last committed state

Pushes all changes in the current directory to a remote repository

Deletes all files in the current directory

Restores the COVID-era salaries of software developers

5/7: How do you unstage changes that were previously staged with git add?

git reset --hard

git restore --staged

git clean -f

git oops

6/7: What does the --amend option do when used with git commit?

Merges the last two commits into one

Allows you to change the message or content of the last commit

Pushes the commit directly to the remote repository

Asks for permission before committing

Hides your credentials from the latest commit

7/7: What is the fastest way to run the previous command in the terminal?

Type the command again, but really fast

Press the F1 key

Press the up arrow key

Superb! Up next, we'll explore tagging and branching, crucial skills for managing different versions and features within your project.

© 2024-2025 GitByBit.All rights reserved.

Course preview Gitopedia Blog

Roadmap

Introduction to version control

What is version control?

Why use version control?

Introduction to Git

Git workflow example

Conclusion and next steps

Command line and terminal

The git command

Configuring Git credentials

Configuring line endings treatment

Configuring default branch name

Conclusion and next steps

Recording changes to the repository

Initializing a repository

Creating work files

Recording changes

Checking the status of the repository

Conclusion and next steps

Resetting unwanted changes

Comparing the working tree with the repository

Discarding local changes

Discarding staged changes

Amending the last commit

Conclusion and next steps

Tagging and branching

Referencing commits

Branches and branching strategies

Creating and switching branches

Merging branches

Conclusion and next steps

Browsing history

Checking the difference between commits

Reverting changes made in older commits

Resetting branches

Conclusion and next steps

Remotes and GitHub

What is a remote repository?

What is a remote repository?

Adding GitHub repository as a remote

Pushing and pulling changes from the remote repository

The danger of rewriting history on a public repository

Conclusion and next steps

Part II: Working in a team ^{coming soon}

Hi! I'm Alex, creator of GitByBit.

This page is part of the interactive course about Git version control.

It's a one-of-a-kind course that is integrated into the VS Code code editor. Learning directly in VS Code lets you operate Git exactly as you would in real life, doing real jobs, writing real code.

In addition, the course has access to your actual terminal, so it can point out mistakes, suggest workarounds, etc.

The course is FREE, there are no Ads or other bullshit. There are optional premium add-ons you can purchase, mainly to support my work (regrettably, I have to eat every day), but that's totally up to you.

Learn Git in VS Code