Git & GitHub
Version control is the one skill every developer is expected to have. Learn how Git really works under the hood — commits, branches, merges, remotes — and how GitHub layers collaboration on top, then remember all of it with spaced repetition.
- flashcards
- 150
- flashcards
- per day
- ~10 min
- per day
- level
- Beginner → Advanced
- level
- modules
- 9
- modules
What are Git and GitHub?
Git is a distributed version control system: every clone carries the full project history, and you record your work as commits — immutable snapshots, not diffs — that chain together into a branchable, rewindable timeline. Once that model clicks, commands like merge, rebase, reset and reflog stop being magic incantations and start being obvious.
GitHub is a hosting platform built on top of Git. It keeps the same repositories and branches, then adds the collaboration layer — pull requests and reviews, issues, releases, GitHub Actions for CI/CD, and governance controls like branch protection, CODEOWNERS and rulesets. Knowing where Git ends and GitHub begins is half the battle.
This track breaks both into bite-sized, practical questions and uses spaced repetition so the distinctions — fetch vs pull, merge vs rebase, reset vs revert — move from "I looked that up once" to genuine recall you can lean on mid-rebase.
9 modules, seed to bloom
Each module is a set of flashcards — 150 in total. Answer, review, and watch your knowledge grow from seed to full bloom.
Core Concepts
Repositories, commits, the staging area, HEAD and Git’s object model
16 cardsBranching & Merging
Branches, merging, fast-forward, rebase, conflicts and tags
16 cardsHistory & Inspection
Viewing history with log, diff, show, blame and bisect
16 cardsRemotes & Collaboration
Remotes, fetch/pull/push, tracking branches, forks and pull requests
16 cardsUndoing & Recovering
reset, revert, restore, stash, clean and the reflog
16 cardsAdvanced Git
Cherry-pick, interactive rebase, submodules, worktrees, hooks and config
16 cardsGitHub Platform
Repositories, issues, pull requests, releases and GitHub Pages
16 cardsGitHub Actions
Workflows, jobs, steps, runners, secrets and reusable actions
16 cardsCollaboration & Governance
Branch protection, CODEOWNERS, roles, orgs and security features
22 cardsSample questions
A taste of the real flashcards. Pick an answer, then reveal the explanation.
Which task needs GitHub, not just Git?
- AOpening a pull request, which is a GitHub feature layered on the Git repo
- BCreating a branch and committing to it without any network connection
- CMerging one branch into another and resolving the conflicts it raises
- DTagging a release commit and then listing every tag in the repository
After a rebase, why do teammates see duplicated commits?
- AYour rebase gave the commits new hashes, so their copies remain
- BYour rebase copied the branch to the remote before merging it
- CYour rebase merged both branches, applying each commit twice
- DYour rebase reset the branch, so the remote restored the old tip
Why is git fetch safer than git pull mid-task?
- AFetch only updates origin/*, leaving your branch and files alone
- BFetch only reports what changed, downloading nothing until a merge
- CFetch refuses to run while the working tree has uncommitted edits
- DFetch keeps the new commits outside .git until you accept them
When two steps run in one job, what do they share?
- AOne runner and its filesystem, so files persist between steps
- BNothing at all, since every step is given a runner of its own
- COne shell process, so exported variables survive by default
- DOne log file only, as each step runs on a separate machine
Learn it once, keep it for good
Answer a question
Each card is one practical concept with multiple options. Pick what you think is right.
Get the full answer
See the correct option plus a clear explanation, and a link to deeper docs when one is available.
Review at the right time
A spaced-repetition engine (SM-2 or FSRS) resurfaces each card just before you would forget it.
Why Git & GitHub are worth your time
The universal developer skill
Every team, every stack, every role touches Git. Fluency here pays off in literally every project you will ever work on.
Understand it, don’t memorize it
Cards build the mental model — the object graph, HEAD, the index — so commands make sense instead of being copied from Stack Overflow.
From first commit to advanced Git
Covers the whole arc: staging and committing, branching and merging, remotes and PRs, undoing mistakes, and power tools like rebase and worktrees.
GitHub Foundations prep
The GitHub platform, Actions and governance modules line up with the official GitHub Foundations exam objectives — a solid recall companion.
Common questions
Who is this track for? +
Anyone who uses version control — new developers building a solid mental model, and experienced engineers filling gaps around rebase, the reflog, remotes, or GitHub Actions. It starts from fundamentals and builds to advanced Git.
Does it cover Git or GitHub? +
Both, and it keeps the line between them clear. Six modules cover Git itself (core concepts, branching and merging, history, remotes, undoing changes, advanced Git); three cover the GitHub platform, GitHub Actions, and collaboration and governance.
Will it help me pass GitHub Foundations? +
It is a study companion, not a course or a practice exam. The GitHub platform, Actions and governance topics overlap heavily with the Foundations objectives, so it pairs well with the official material for spaced-repetition recall.
Is it free? +
Yes, completely free. No registration or credit card is required, and all your progress is stored locally in your browser.
Ready to master Git & GitHub?
Plant your first seed today. Ten minutes a day turns Git from a source of fear into a tool you actually understand.