Distributed Source Control Concepts — Think Global, Commit Local
Fetch vs pull, remote tracking branches, and understanding Git's distributed architecture
Here's something that surprises most developers: when you make a commit, it only exists on your machine. When you check git log, you're looking at your local history. When you create a branch, it's local only.
Git is a distributed version control system. That means every developer (and every worktree, and every clone) has a complete, independent copy of the repository. There is no "central server" in Git's architecture — there are just copies that sync with each other.
GitHub isn't the repository. It's just another copy that everyone agrees to use as the shared meeting point. Understanding this distinction is the key to understanding fetch, pull, push, and why your local main can be different from origin/main.
Local vs Remote — Two Different Worlds
Your Git repository has
This lesson is part of the Guild Member curriculum. Plans start at $29/mo.