Git Internals

Remote-Tracking References

Understand the difference between `main` and `origin/main` so fetch, pull, push, and branch sync become easier to reason about.

Many sync mistakes come from not separating these two names:

  • main: your local branch
  • origin/main: your local record of the remote state

Why fetch matters

git fetch updates the remote-tracking ref, not your working branch. That separation is what lets Git say:

  1. learn what changed upstream
  2. decide how to integrate it locally

Why this helps with pull

git pull is fetch plus integration. The better you understand remote-tracking refs, the easier it becomes to reason about why pull merges, rebases, fast-forwards, or stops.

Related Reads

Git Object Database

Understand blob, tree, commit, and tag objects, and why Git describes itself as a content-addressable object database.

Working Tree, Index, and Object Store

Separating the working tree, index, and object database is the clearest way to understand add, commit, restore, and reset.

Git References and HEAD

Put branches, tags, remote-tracking refs, and HEAD into one model so Git's pointer behavior becomes easier to reason about.

PreviousGit References and HEAD

Put branches, tags, remote-tracking refs, and HEAD into one model so Git's pointer behavior becomes easier to reason about.

NextGit Commit Graph and History Shape

Understand why Git history is fundamentally a graph rather than a simple timeline, and how merge and rebase reshape that graph.