What Git Actually Is (and Isn't)
Version control in plain terms, why "final_v2_USE_THIS.docx" is the problem git solves, and a first look at this site's own commit history.
Technicians
Eight sessions on version control: what it is, the daily habits, branches and merges, and the two things that will actually get someone in trouble, a public repo and a secret in a commit. This training site is the running example throughout, including how a push from this laptop turns into the page you're reading.
Version control in plain terms, and the real path from a commit on this laptop to the page you are reading.
Version control in plain terms, why "final_v2_USE_THIS.docx" is the problem git solves, and a first look at this site's own commit history.
Repos, remotes, and the real path from a commit on this laptop to the page Entra lets you into: GitHub to Cloudflare Pages to the sign-in screen.
The loop you run every day, branches that keep your work apart, and bringing it back together.
Status, add, commit, push, pull, and writing a commit message somebody else can use six months from now.
A line of work that doesn't touch anyone else's, why main stays safe to publish, and today's near-miss between two people editing the same file.
Bringing two lines of work back together, and reading a merge conflict as a Tuesday problem, not an emergency.
Testing without touching what staff see, keeping secrets out of the repo, and where a repo should live.
Mapping a branch to your own private copy of the site and main to what staff actually see, so a broken test never reaches anyone.
Why a repo has to stay private even behind Entra, what never belongs in a commit, and what to do the moment a secret leaks anyway.
Two systems that both think they own the one true copy, what that fight looks like, and where a repo should actually live on disk.