3. Recording changes to the repository

Conclusion and next steps

Now that we've learned how to save new changes into the repository, let's see how we can revert unwanted changes in our working tree. Oh, wait, I almost forgot...

Quiz time!

Quiz yourself

1/6: What command initializes a new Git repository in the current directory?
2/6: What is the working tree in Git?
3/6: What does the git add command do?
4/6: What does the -m option do when used with git commit?
5/6: Why is it beneficial to split independent changes into separate commits?
6/6: What does a clean working tree mean?

Amazing work! In the upcoming chapter, we'll explore how to undo changes and revert to previous versions of your project. Get ready to become a Git time traveler!

Next step
© 2024-2025 GitByBit.All rights reserved.

Hi! I'm Alex, creator of GitByBit.

This page is a 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