Git flashcards

Save every version of your code, undo any mistake and ship with a team without stepping on each other.

Beginner friendly, starts from zero

CardsCheatsheetTips and tricks

GitStart from zero · 1 of 12

What is Git, in one plain sentence?

Think of the answer, then tap

A tool that saves the history of a project, so you can see every change, go back to any earlier version and work with others on the same files.

Undo for a whole project, forever.

Show again

12 left

Got it

Drag the card: right if you know it, left to see it again, up to skip · Space turn over · K got it · J again · ← back

Tap to turn over. Swipe right if you know it, left to see it again.

All topics

What you will learn

Start from zero
- Why version control exists4 cards
- The key words5 cards
- Getting ready3 cards
Core basics
- Setting up a repository5 cards
- Making commits5 cards
- Reading history2 cards
- Branches3 cards
- Working with remotes3 cards
Next steps
- Syncing and resolving conflicts4 cards
- Undoing changes6 cards
- Finding things in history3 cards
- Team workflow and releases5 cards
Go deeper
- Rewriting history safely4 cards
- Debugging and merge strategy3 cards
- Large repos and multiple checkouts6 cards
- Security, policy and automation5 cards

Final test and certificate

10 questions drawn fresh from the whole topic, about 15 minutes. Sign in, score 80% or more and get a free certificate with your name and a public check link anyone can open, such as an employer or a teacher. Not signed in? Try a practice test from the cards.

Take the final test

About these cards

Reviewed 26 October 2026
CoversGit 2.56Git LFS 3

Checked against

How these cards are made

Git at a glance

Git saves the full history of a project, so you can go back to any version and work with a team safely.

Like a photo album of your project: each step gets a captioned photo you can flip back to.

Words you will meet

Repository: Your project folder plus its saved history
Commit: One saved snapshot of the files with a short message
Staging area: A waiting tray for changes that go into the next commit
Branch: A separate line of work that does not touch the main version
Merge: Join a finished branch back into another one
Remote: A shared copy of the repo on a server
Push and pull: Send your commits to the remote, or bring others' commits to you
Diff: A view of exactly which lines changed

The steps

1. Start from zero (12 cards): What Git is, the key words in plain English, and your first commit.
2. Core basics (18 cards): Snapshots, the three areas, branches and your first push, the way teams really use them.
3. Next steps (18 cards): Conflicts, undoing anything safely, stash, rebase and a pull request workflow you will use every week.
4. Go deeper (18 cards): History surgery, recovery, bisect, internals, signing, monorepo speed and team-scale conventions.

All 12 cards in Start from zero

What is Git, in one plain sentence?: A tool that saves the history of a project, so you can see every change, go back to any earlier version and work with others on the same files.
How did people manage versions before Git?: They copied folders and named them final, final-2, final-really. Nobody knew which was newest, and two people editing the same file wiped out each other's work.
Where do you already meet the idea behind Git?: Version history in an online document, where you can open yesterday's copy, or the undo list in a drawing app. Git does this for every file in a project.
What is an everyday picture for how Git works?: A photo album of your project. Each time you are happy with a step, you take a photo with a short caption. You can always flip back to any old photo.
What do repository and commit mean?: A repository (repo) is your project folder plus its saved history. A commit is one saved snapshot of the files with a short message saying what changed.
What is the staging area?: A waiting tray where you place the changes you want in your next commit. You choose what goes in, so one commit holds one clear change.
What do branch and merge mean?: A branch is a separate line of work, so you can try something without touching the main version. Merge joins a finished branch back into the main line.
What are a remote, push and pull?: A remote is a copy of the repo on a server (a computer online) that the team shares. Push sends your commits up to it. Pull brings other people's commits down to you.
What are a host, a pull request and a diff?: A host is a website that keeps remotes, such as GitHub or Bitbucket. A pull request asks teammates to review your branch before it is merged. A diff shows exactly which lines changed.
What do you need before starting?: Git installed (it comes with many computers) and a terminal, a text window where you type commands. A free host account helps later for sharing.
What is a first tiny win with Git?: git init starts a repo in your folder, git add puts a file in the staging area, and git commit -m saves the snapshot with a message.
What will you be able to do after this topic?: Save clean commits, undo mistakes, work on branches, merge them, share your work through a remote and fix the common errors teams hit every week.

Git cheatsheet

Daily loop

git status -sb Short status with branch and ahead/behind
git add -p Stage changes hunk by hunk
git diff --staged Review what will be committed
git commit -m "subject" Commit staged changes
git pull --rebase Update and keep history linear
git push -u origin HEAD Push current branch and track it

Branches

git switch -c feat/x origin/main New branch from latest main
git switch - Jump back to previous branch
git branch -vv Branches with upstream and ahead/behind
git rebase -i origin/main Squash, reword, reorder before PR
git merge --ff-only origin/main Update main, never create a merge
git fetch --prune Drop refs deleted on the server

Undo

git restore <file> Discard unstaged edits
git restore --staged <file> Unstage, keep edits
git commit --amend --no-edit Add staged changes to last commit
git reset --soft HEAD~1 Undo last commit, keep it staged
git revert <hash> Undo a shared commit with a new one
git reflog Find any commit HEAD has visited
git stash push -u -m "msg" Shelve all changes incl. new files

Investigate

git log --oneline --graph --all Visual history of every branch
git log -S "text" -- path Commits that added or removed text
git log main..feature Commits on feature not on main
git blame -w -C -L 10,30 file Who changed lines, ignoring moves
git show <hash> --stat Files changed in a commit
git bisect run <test-cmd> Auto-find the breaking commit

Remote and release

git push --force-with-lease Force push only if nobody else pushed
git tag -a v1.4.0 -m "msg" Annotated release tag
git push --follow-tags Push commits and their annotated tags
git cherry-pick -x <hash> Copy one commit, note the source
git worktree add ../dir branch Second working folder, same repo
git clone --filter=blob:none URL Fast clone, fetch files on demand