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
- 144
- 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 — 144 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
16 cardsSample questions
A taste of the real flashcards. Pick an answer, then reveal the explanation.
What is the relationship between Git and GitHub?
- AGit is the version control tool; GitHub is a hosting platform built on top of it
- BGit is the hosting platform; GitHub is the command-line tool that talks to it
- CThey are two names for the same distributed version control command-line tool
- DGit is an older protocol that GitHub fully replaced with its own version system
What is a key difference between merging and rebasing?
- AMerge preserves history with a merge commit; rebase rewrites it linearly
- BMerge rewrites history linearly; rebase adds a commit with two parents
- CMerge works only on local branches; rebase works only against a remote
- DMerge requires resolving conflicts; rebase can never produce a conflict
What is the difference between git fetch and git pull?
- AFetch only downloads changes; pull downloads and integrates them into your branch
- BFetch downloads and integrates changes; pull only downloads them for later review
- CFetch works on tags only, while pull works exclusively on branch commits instead
- DFetch requires a clean working tree, while pull can run with local edits present
What is a job in a GitHub Actions workflow?
- AA set of steps that run together on the same runner as a single unit
- BA single shell command that is executed once when the workflow is triggered
- CThe reusable action that is published so other repositories can call into it
- DThe event definition that decides when the whole workflow itself should start
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.