Git quizzes
Version control every developer is expected to know.
Practise Git with short quizzes that mix concept checks, code reading and debugging.
Git quiz levels
Difficulty rises through concepts (code reading, debugging, edge cases, trade-offs), not through trick wording.
- Beginner
Core vocabulary and fundamentals.
- Git Basics · 7 questions
- Git Workflow Lab · 5 activities
Topics covered in the Git quizzes
Every topic below appears in at least one question today. The number is how many questions cover it.
- Undo · 2
- Ignore rules · 1
- Merging · 1
- Rebase · 1
- Remotes · 1
- Staging · 1
How this works
Practice or exam mode
Practice mode explains each answer straight away. Exam mode holds all answers until you finish, then shows a full review.
Shuffled answer order
Options are shuffled on every attempt, so you learn the idea rather than the position of the right letter.
Timer, flags and skips
A timer runs while you play. Flag questions to revisit them, or skip and come back from the question navigator.
Saved on your device
Scores, streaks and topic accuracy are stored in your browser only. There is no account.
Learn Git first, or keep going
Git quiz FAQ
How many Git quizzes are there?
There are currently 1 multiple-choice Git quizzes with 7 questions in total, plus 1 interactive challenge. The numbers on this page come from the live quiz catalogue.
Which Git quiz should I start with?
Start with Git Basics, the beginner-level quiz.
Are the Git quizzes free?
Yes. There is no sign-up. Your scores and streaks are stored in your own browser.
Do the Git quizzes explain the answers?
Yes. Every question has an explanation covering why the right answer is correct and why the tempting alternatives are not.
Is this about GitHub?
These quizzes cover Git itself. Hosting features such as pull requests are not included.
Will this teach me how to resolve merge conflicts?
We test your conceptual understanding of why conflicts happen and how Git tracks changes. Interactive conflict resolution is best learned in an actual terminal.
Why do you ask about the "three areas"?
Because understanding the working tree, the index (staging area), and the commit history is the key to never losing your work in Git.