Git & GitHub Challenges

A learning path tells you what to read in what order. A challenge adds a day: one lesson, one objective you can check, a lab where there is one, and a next action. Nothing here is new content — every day points at a lesson or lab that already exists — and nothing is gated.

7-Day Git ChallengeOne week from "I run the commands" to "I know what they do" — the object model, the three places a change can live, and the two recoveries everyone eventually needs.7 days · 4 labs14-Day GitHub Engineering ChallengeTwo weeks across pull requests, code review, CODEOWNERS, rulesets, the GitHub CLI, the API and the security settings that matter — ending with a pull request workflow you designed and tested.14 days · 2 labs30-Day Modern Git & DevOps ChallengeA month in five arcs — history and branching, GitHub Actions, Actions security, supply chain and secrets, then infrastructure through Git — with a lab on thirteen of its days.30 days · 13 labs

Note

Tick a day when you have done it, not when you have read it. Progress is stored in this browser and appears on My Academy; it can be exported to another device.

How to choose

7-Day Git if you use Git daily and could not explain what git reset --soft does to the index. Beginner to intermediate.

14-Day GitHub Engineering if Git is fine and the gaps are GitHub — review, CODEOWNERS, rules, the CLI, automation. Intermediate.

30-Day Modern Git & DevOps if you want the whole modern workflow: rebasing done right, Actions from first workflow to OIDC, secrets and supply chain, then infrastructure through Git. Intermediate to advanced, and the lab on thirteen of its days is the point.