Git & GitHub
The difference between a student project and something a team can ship. Branching, PRs, rebase, and the incidents you'll cause if you skip this.
Mastery unlocks after a 90% Quiz score
Real-world analogy
Git is a time machine with a shared calendar. Branches are parallel timelines. Merge is the meeting where those timelines have to agree.
◎ Why it matters in production
Force-pushing to main, committing secrets, and 400-file PRs are how juniors lose trust in week one. Companies assume Git fluency. Curriculum rarely teaches it.
Fundamental concepts you will master
Snapshots, not diffs
Every commit is a full tree. That's why checkout, revert and bisect feel instant.
The three trees
Working directory, staging, repository — most Git confusion is mixing these three up.
Branching models
Trunk-based vs Gitflow. What your first team will actually use.
Review culture
A PR is a conversation. Small diffs, clear intent, and a description a reviewer can trust.
Step-by-step curriculum
Init to first push
Clone, status, add, commit, log — and the anatomy of a useful commit message.
Branching without fear
Create, switch, merge, delete. Fast-forward vs a merge commit.
Pull requests
Open, review, address comments, squash. The social protocol of shipping.
Rebase & conflicts
When to rebase, when not to, and how to resolve a conflict without panic.
Incidents
Undo a commit, recover a branch, rotate a leaked token.
Ready to see it in action?
Build your own path, step through operations, and watch mastery unlock after 90%.
Pointer Phantom
Direct Byte Access
+1,250 XP → Cache Ghost