The big picture
GitHub is a shared home for work that changes over time. It keeps every saved version, makes proposed changes visible, and records who decided what.
● Built for smart people who don't speak developer
GitHub finally
makes sense.
A hands-on training gym that takes you from “What's a repo?” to confidently following work, reviewing changes, and leading a GitHub-powered team.
8 guided modules74 focused minutes0 setup required
github.com / northstar / launch-site
northstar/launch-site
PrivateCodeIssues 7Pull requests 2Actions
✓
OPEN PULL REQUEST #52
Update Q3 customer launch date
maya wants to merge 1 commit into main from docs/update-launch-date
M
Maya proposed a changeWhat changed · Why it matters · How it was checked
9:42✓
All checks passedLinks valid · Preview ready
9:43R
You approved the changeScope, evidence, and launch timing confirmed
9:51✓ Ready to merge
PLAIN ENGLISH
A pull request is a proposal asking: “Should this change become official?”
The real problem
Most GitHub training teaches clicks. This teaches judgment.
Knowing where the green button lives is not enough. You need a mental model for what the team is changing, why review exists, and which signals deserve your attention.
01Idea→
02Issue→
03Branch→
04Commit→
05Pull request→
06Review→
07Main
Every important change leaves a visible, reviewable trail.
Zero to workflow-ready
One idea. One move.
One win at a time.
Each module translates the concept, shows why it matters at work, then puts you inside a safe GitHub simulation. The next module unlocks when you prove the move.
Repository tour
A repository brings the work, its history, the team conversation, and the automation into one place. You can learn a project’s health without opening a terminal.
Changes & commits
A commit is not an auto-save. It is an intentional checkpoint that groups one coherent change and explains why that change exists.
Branches
A branch is an independent line of work. It starts from the current official version and lets someone prepare a change without altering main for everyone else.
Pull requests
A pull request—usually called a PR—is a proposal to merge one branch into another. It packages the change, context, conversation, checks, and approvals into one decision record.
Review & conflicts
A review tests whether the proposal solves the right problem safely. Reviewers inspect the diff, ask questions, check evidence, and then comment, approve, or request changes.
Issues & projects
Issues capture work, decisions, bugs, or ideas. Projects organize issues and pull requests into useful views such as a roadmap, table, or board.
Final assessment
Healthy teams make the safe path the easy path: protected branches, required reviews, automated checks, least-privilege access, and fast response when a secret is exposed.
Built for the person responsible
You don't need to become a developer.
You need enough fluency to ask better questions, see delivery risk early, and participate in the decisions GitHub records.
Start module one →Read the room
Navigate any repository and identify the work, owner, status, and risk.
Make the call
Understand changes, checks, reviews, conflicts, and when a PR is safe to merge.
Lead the system
Use issues, projects, permissions, and guardrails to make delivery visible.
Your first safe rep
Open the gym.
Leave the jargon outside.
Start with the mental model, finish with a leadership assessment, and keep your progress on this device. No signup required.
Begin the GitHub course →Preview the leadership field guide