Is GitQuest suitable for all types of training programs?

Yes. Whether it's an intensive 3-month bootcamp, a 12- to 24-month apprenticeship or a university degree, GitQuest adapts thanks to its modular progression. Learners advance at their own pace.

How long does it take to cover Git basics with GitQuest?

The basics (init, add, commit, push, pull) are covered in the first 5 investigations, roughly 2 to 3 hours of practice. Advanced concepts (branches, merge, rebase) require about ten additional hours.

Is Git really the main stumbling block in training?

Yes, in our field experience. Git is often the first tool that confronts learners with the command line, English error messages and abstract concepts like branches. It's a significant dropout factor.

Can GitQuest be used as course material?

Absolutely. GitQuest is designed as a complement to existing courses. Instructors can direct their learners to specific investigations based on the curriculum. Check our instructors page for more details.

Do learners need a computer?

No, GitQuest works on mobile. The simulated terminal lets learners practice Git commands without any installation. It's ideal for learners who don't always have access to a computer outside of class.

Git for developer training programs

Git is the first collaborative tool learners encounter in training. GitQuest makes this learning progressive, hands-on and motivating.

Get started free Instructors page

gitquest — enquête

Why Git is a stumbling block in training

After years of hands-on training experience, the observation is clear: Git is one of the primary sources of frustration and dropout among developer learners.

Too abstract

Concepts like staging area, HEAD, and detached state are hard to visualize without practice.

Cryptic messages

Git error messages are technical and often anxiety-inducing for beginners.

Fear of breaking things

Learners are afraid of losing their code. They avoid Git instead of getting comfortable with it.

Not enough practice

Curricula often dedicate less than 10 hours to Git across programs lasting 6 to 24 months.

The solution

Learn Git through investigations, not lectures

GitQuest transforms Git learning into interactive investigations. Each scenario puts the learner face-to-face with a concrete problem to solve using Git commands.

No more copy-pasting from a tutorial. The learner must understand the situation, choose the right command and observe the result. Learning is active, not passive.

The XP and level system maintains motivation over time, a key factor in longer training programs.

gitquest - investigation

# Investigation: The missing file

$git log --oneline --all

a3b4c5d (HEAD -> main) Accidental deletion

f6g7h8i Add config.json file

$git checkout f6g7h8i -- config.json

config.json restored successfully!

$git commit -m "fix: restore config.json"

Well done! File recovered. +60 XP

Adapted to every training format

Whether your program lasts 3 months or 3 years, GitQuest fits into your curriculum.

3 to 6 months

Bootcamps

In a bootcamp, every hour counts. GitQuest lets learners practice Git outside of class hours, on mobile, without taking up instruction time.

Quick progress on basics in 1 week
Teamwork scenarios from week 2
Git autonomy for group projects

12 to 24 months

Apprenticeships

Apprentices juggle between school and work. GitQuest ensures continuous practice and reinforces the skills expected in the professional environment.

Scenarios based on real workplace workflows
Progression spread over the full contract duration
Professional certification skills covered

2 to 5 years

Universities

Long programs have time to go deeper. GitQuest brings the hands-on practice often missing from theoretical lectures and labs.

Complement to lectures
Preparation for internships and first jobs
Advanced concepts: rebase, cherry-pick, bisect

Git skills covered by GitQuest

A structured progression covering all Git skills expected in developer training.

Fundamentals

Initialize a repository (git init)
Add and commit files
Understand the staging area
View history (git log)
Work with a remote repository (push, pull)

Collaboration

Create and manage branches
Merge branches (merge)
Resolve conflicts
Use pull requests
Apply a Git Flow workflow

Advanced

Rewrite history (rebase)
Select specific commits (cherry-pick)
Find a bug (bisect)
Stash work (stash)
Recover lost commits (reflog)

Best practices

Write clear commit messages
Structure branches properly
Use .gitignore correctly
Make atomic commits
Document your changes

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

Questions fréquentes

Integrate Git into your training

GitQuest is the ideal complement to your development courses. Free for learners.

Get started now