Commit
In Git, a commit is a snapshot of your project's files at a point in time. Commits are the building blocks of your project's history. When you make changes to your project, you can group them into a commit. Such a commit represents a set of changes that you want to save—this could be changes to existing files, new files, or deletions of files. Besides the changes themselves, a commit usually includes a commit message, which is a brief description written by the developer to explain what was changed and why.
A chronological chain of commits forms a timeline of your project's development. It is helpful for understanding how the project evolved over time, who made changes, and why. You can reconstruct the state of your project at any point in time by checking out a specific commit.
Each commit is associated with a unique ID, called a hash (e.g. 346ca091076783c70623aba03fb7139d3d27134f or shortened 346ca09), which lets you identify and access the commit. This hash acts like a fingerprint for that specific set of changes.
Hi! I'm Alex, creator of GitByBit.
And this is Gitopedia—a reference that summarizes knowledge in my Git course.
Gitopedia is designed to be a personal knowledge base. When you progress through the main Git course in VS Code, you unlock all of these topics, one by one, bit by bit. This gives you time to digest the information and gradually build the mental model of Git. Here's an example of how it works:
Learning directly in VS Code lets you practice 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.