GitSetGo — learn git the fun way - 30 levels, real commands, one grumpy mentor

by•
GitSetGo teaches Git by making you actually type commands, not pick multiple choice. Play a new intern reporting to Mr. Torvalds, clearing 30 levels against a simulated repo with real file states, staging and commit history. New since our first PH launch: a full UX overhaul (screen reader + reduced-motion support, mid-station resume), a daily Git puzzle with streaks, a 30-command reference (GitDex), 6 learning paths, and a verifiable certificate for LinkedIn, co-brandable via your college.

Add a comment

Replies

Best
Hey Product Hunt — Abhishek here, solo dev on GitSetGo. We actually posted here once before, back in June, and it landed with 2 points and not much else. I'm not going to pretend that didn't sting a little, but looking back, the app didn't deserve much more — half of what's in it today wasn't built yet. So this isn't a "we're back" post for the sake of it. Since June we did a full accessibility and UX pass (screen reader support, reduced motion, a station that remembers where you stopped so you're not replaying a level because you got a phone call), and we shipped four things people had actually been asking for: a daily Git puzzle with streaks, a 30-command reference called GitDex, six guided learning paths depending on what you're trying to learn, and a certificate you can put on LinkedIn when you finish — colleges can even put their own name on it if they partner with us. The reason I built this in the first place: I watched too many junior devs (and, a few years ago, myself) learn Git by memorizing commands off a cheat sheet, then panicking the first time a merge went sideways. Reading about git reset --hard and typing it while your afternoon's work is on the line are two completely different kinds of learning. GitSetGo is 30 levels built around that second kind — a mentor named Mr. Torvalds walks you through what broke and why, on a simulated repo where breaking things costs nothing. Still free, still no account needed to play. If you've ever taught Git to someone and watched them get stuck at the same three commands everyone gets stuck at, I'd really like to hear which ones — that's basically our roadmap at this point.