How Git Works

Branches Demystified
Welcome to How Git Works, Module 2. This is where things really get interesting. In the previous module, we laid the groundwork. Now let's make that information concretely useful. In Module 1, we said that Git is a stupid content tracker. We had this method for an onion, now we can move on to the next layer of the Git onion, and look at the features that turn Git into a full-fledged revision control system, features like branches and merges. I'm assuming that you already have a basic idea of what a branch is. Maybe you even use Git branches every day. But after this module, you might end up looking at them in a different light.

Rebasing Made Simple
Welcome to How Git Works, Module 3. Git is an onion, remember, and we're still looking at the versioning layer of the onion, the features that turn Git into a full-fledged version control system. In the previous module, we talked about branching and merging. Now, let's look at a couple more features that are also related to versioning, and in particular at a very important one, rebasing. Branching and merging are standard features for any revision control system, but rebasing is way less common. Only a handful of version control systems have it, and Git is by far the most popular of them. In a way, rebasing can be seen as Git's signature feature. Let's see how it works.

Distributed Version Control
Hello and welcome to How Git Works, Module 4. We are only missing one last layer in our description of the Git onion, but it's a really important one, distribution. So far we imagined that there was only one computer in the world, the computer that you're running Git on. Now, let's see what happens if you use Git the way it's used in practice, to share a project across multiple computers.