Skip to main content
Kill -9 Club
Sign in
Intermediate6 lessons127 minutes

Git for administrators: a history you can trust

Answer "what changed?" with a command instead of a memory: commits, history, remotes and release tags.

Every incident opens with the same question: what changed? This course makes that a command instead of a memory. A commit is a snapshot, not a diff; a history is interrogated with log, diff and blame; and a committed secret does not go away because the file was deleted — this course explains why, and what to do instead.

What you will be able to do

  • Create a repository, build a commit deliberately, and say what a commit actually contains
  • Answer "what changed?" with log, diff, show and blame
  • Keep secrets and generated files out of history — and respond correctly when it is too late
  • Move history between machines with clone, fetch, pull and push, over SSH
  • Name deployable states with annotated tags

Outline

  1. 01

    A history you can trust

    What a commit is, how to interrogate history, and what never goes in.

  2. 02

    Moving history between machines

    Remotes over SSH, branches read without fear, and release tags.

Technical content last reviewed on 9 August 2026