Git & Version Control
The model underneath the commands, and the branching argument every team has.
5 topics
The Git mental model
Git stores immutable snapshots in a DAG and moves labels around them, which explains almost every command you find confusing.
core25 minBranching strategies
Trunk-based development with short-lived branches beats Git Flow for most product teams, and you should be able to say why.
core20 minMerge, rebase & readable history
Rebase your own unpushed work to keep history linear, merge anything shared, and never rewrite a branch other people are building on.
core20 minCommit & pull request hygiene
A commit should be one reversible idea with a message explaining why, and a PR should tell the reviewer what to look at first.
core18 minRecovering from Git mistakes
Almost nothing committed is ever truly lost — reflog, revert and bisect cover the situations that actually cause panic.
core18 min