Git Fundamentals: From Zero to Repo

Niki just joined 404 Labs as a junior developer. Her onboarding project is beacon-api, a small Go service the team runs in production. Every challenge in this path picks up where the last one left off, inside the same repository, following the same commit history.

Git is not taught here as a list of commands. Each day starts with something that goes wrong: an uninitialized project, a typo in a commit message, work sitting on the wrong branch, a secret key left in plain text. The fix is the lesson.

More days get added as Niki's first weeks continue.

Niki's first day. The beacon-api folder exists, but nothing in it is under version control yet.

Two unrelated changes, tangled into one edit, plus a file that never made it into the commit at all.

Yesterday's commit message has a typo, still unpushed, and today's fix should never have been a commit of its own.

Forty minutes of uncommitted work, sitting directly on main, again.

A committed build binary, stray junk files, and a plaintext key sitting in the open, right before Niki's first pull request.

In progress...