Do I need to do the investigations in order?

It's recommended for beginners: investigations are sorted by increasing difficulty and progressively introduce new commands. But if you already have a foundation, you can jump straight to intermediate or advanced investigations.

What happens if I get stuck on an investigation?

The system offers progressive hints: first a vague indication, then increasingly specific ones. You'll never receive the answer directly, but you'll be guided toward the solution. You can also consult the built-in glossary at any time.

How long does an investigation take?

Between 5 and 20 minutes depending on difficulty and your level. Beginner investigations take 5 to 10 minutes, advanced ones can take up to 20 minutes. Each investigation is saved: you can resume it later.

Are the investigations based on real-world situations?

Yes. Each investigation is inspired by a real Git problem encountered in the workplace: a commit lost after a reset, a branch deleted before merging, a complex merge conflict, a sensitive file committed by mistake. You learn to solve problems you'll actually face.

Can I redo an investigation to improve my score?

You can redo any investigation. XP is only awarded the first time, but you can practice without limits. It's an excellent way to verify you've truly mastered the commands.

Git investigations: solve mysteries with your commands

Run interactive investigations to learn Git. Missing commits, lost branches, impossible merges: each mission is a mystery to solve in the terminal.

Launch my first investigation View investigations

gitquest — enquête

50+

Available investigations

Difficulty levels

XP per completed investigation

15 min

Average duration

Learn Git by investigating

Forget tutorials where you copy commands without understanding. In GitQuest, each exercise is an investigation: a realistic scenario with a problem to solve.

A commit has disappeared? A branch was deleted by mistake? A merge went wrong? It's up to you to lead the investigation using the right Git commands.

Each investigation teaches you new commands in context. You don't memorize a list: you understand when and whyto use each command.

Realistic scenario

Each investigation is inspired by a real problem encountered in the workplace.

Progressive resolution

You progress step by step, with hints if you get stuck.

Commands in context

You learn when and why to use each Git command.

Example: The phantom commit

Follow the walkthrough of a complete investigation, from the initial clue to the resolution.

gitquest — investigation #1

# Investigation: The phantom commit

A developer claims they made a commit last night.

But it no longer appears in the log. Find it.

$git log --oneline -5

a1b2c3d Fix bug #42

f8e7d6c Update README

b9a8c7d Add unit tests

# The commit is not in the log... Let's use reflog

$git reflog

a1b2c3d HEAD@{0}: reset: moving to HEAD~1

e4f5g6h HEAD@{1}: commit: Add payment system

# The commit was erased by a reset! Let's restore it.

$git cherry-pick e4f5g6h

Commit restored! Investigation solved. +75 XP

Three difficulty levels

Investigations adapt to your level. Start with the basics and progress toward increasingly complex scenarios.

Beginner15+ investigations

First steps

Guided investigations to discover basic commands: git log, git status, git diff, git add, git commit. Each step is explained.

Duration: 5 to 10 minutes

Intermediate20+ investigations

Investigation

More complex scenarios involving branches, merge, stash and conflict resolution. Hints are less direct.

Duration: 10 to 15 minutes

Advanced15+ investigations

Expertise

Investigations that combine multiple advanced commands: rebase, cherry-pick, bisect, reflog. Few hints, lots of thinking.

Duration: 15 to 20 minutes

Sample investigations

Here is a preview of the missions that await you. Each investigation teaches specific commands.

Beginner50 XP

The phantom commit

A commit has disappeared from the history. Use git reflog to find it and restore it.

git loggit refloggit cherry-pick

Beginner50 XP

The lost branch

A feature branch was deleted by mistake before the merge. Find it and merge it.

git branch -agit refloggit checkout -b

Intermediate65 XP

The impossible merge

Two branches have conflicting changes. Resolve the conflict and complete the merge.

git mergegit diffgit addgit commit

Intermediate70 XP

The secret file

A sensitive file was committed by mistake. Remove it from the history without losing other changes.

git loggit rebase -igit filter-branch

Advanced85 XP

Time travel

A bug was introduced somewhere in the last 50 commits. Use git bisect to find it.

git bisect startgit bisect goodgit bisect bad

Advanced90 XP

The cursed rebase

An interactive rebase went wrong. Rebuild the history cleanly from the reflog.

git refloggit resetgit rebase --onto

Git investigations in the app

Here is what investigations look like in GitQuest. Story-driven missions with a real built-in terminal.

List of Git investigations with difficulty levels

Simulated terminal during a Git investigation

Tablet view of GitQuest investigations with mission details

GitQuest is created by Anaïs (nouvelle fenêtre), web developer and head of education, specializing in tech training and digital accessibility.

Questions about Git investigations

Ready to investigate?

Launch your first Git investigation for free. No installation required.

Start the investigation