what version control actually solves

Version control keeps a full history of every change to a set of files, who made it, and why — so nothing is ever truly lost, and multiple people can work on the same content without overwriting each other. Older systems (like CVS or SVN) were centralized: one server held the real history, and you needed a network connection to see it or commit to it. Git is distributed — every clone has the entire history, so commits, branches, and even most of your daily work happen fully offline, syncing with others only when you push or pull.

git

github

gitconfig

gitignore

Git Internals

What's actually inside .git — objects, refs, the index, and the commit graph.

Undoing Things in Git

Reflog, reset vs. revert, and recovering a deleted branch — probably the most-searched git topic there is.

Git Hooks & Automation

Running checks automatically at commit and push time, and sharing them across a team.

Git LFS

Why large binary files (datasets, model checkpoints) don't belong directly in git history.

Worktrees & Submodules

Multiple working directories from one repo, and embedding one repo inside another.

related topics

IDE & Text Editor Notes — the editor most of this version-controlled code is written in.