Course
Git in Practice
The git a working engineer actually uses: history as a tool, rebase vs merge with judgment, bisect for regression hunts, reflog for recovery, hooks, and signed commits for supply-chain trust.
History as a Working Tool
Read history like a database, commit like you mean it, and reshape work before anyone sees it.
- 01Reading git log Like a ProfessionalQuery history instead of scrolling it: graph views, pickaxe search, blame that survives reformats.25mOpen
- 02Atomic Commits and Messages That Age WellStage hunks with add -p, write messages that record why, and keep secrets out of history.20mOpen
- 03Interactive Rebase: Cleaning Up Before You PushSquash, fixup, and reorder commits with rebase -i and --autosquash — plus where the landmines are.35mMembers
Rewinding, Recovering, and Hunting Bugs
Undo changes safely, bisect regressions to a single commit, and rescue work you thought was gone.
- 01revert vs reset vs restore: Undo Without RegretThree commands that all mean 'undo' — and why only revert is safe on shared history.25mMembers
- 02git bisect: Hunting Regressions on PurposeBinary-search history with bisect run and a pass/fail script to name the first bad commit.30mMembers
- 03reflog: The Undo History for Your HistoryRecover deleted branches, bad rebases, and dropped stashes from HEAD's private journal.25mMembers
Collaborating Cleanly and Safely
Choose rebase or merge on purpose, automate with hooks, and sign your work for supply-chain trust.
- 01Rebase vs Merge: Choosing With JudgmentThe golden rule and its real exception, --force-with-lease, and matching the tool to the situation.30mPremium
- 02Git Hooks and CI Checks: Automating Disciplinepre-commit, commit-msg, and pre-push hooks — and why enforcement actually belongs in CI.30mPremium
- 03Signed Commits and Supply-Chain HygieneWhy author fields are forged in one flag, SSH commit signing, and where provenance fits in defense.30mPremium