Git Basics: Commits, Branches, And Why “Distributed” Matters

**Git** is a free, open-source distributed version control system maintained in the `git/git` project; documentation lives at `git-scm.com` and in the built-in `git help` pages. Each **commit** is a snapshot identified by a cryptographic hash; **branches** are movable pointers to commits, not separate file copies.

“Distributed” means every clone carries full history (subject to shallow clone options). **Merge** creates a commit that joins histories; **rebase** replays commits onto a new base, rewriting commit IDs. Both are standard operations; team policy chooses which to prefer on shared branches.

This article does not recommend a branching model (Git Flow, trunk-based, etc.); it states mechanics you can verify in official Git documentation before adopting workflow rules.