$ Git Game

A multiplayer card game whose rules are Git.

Ship commits to a shared main. Pull before you push, blame the bugs you can't see, and survive git push --force. Free, in your browser, with nothing to sign up for.

play the bot now or open a room for friends

ana@main $ git pull --rebase -X ours
Successfully rebased and updated refs/heads/main.
ana@main $ git push
3f2c1d9..8e1da02 main -> main
bot@main $ git push
! [rejected] main -> main (non-fast-forward)
bot@main $ git push --force
+ 8e1da02...b0ba026 main -> main (forced update)
ana@main $ git reflog
# restored 8e1da02: back on top of main
commitauth.js+5 commitapi.py+6BUG commitstyles.css+3 commandpush --force

For people who know nothing about Git, or coding

What this is, in plain words

Programmers work on one thing together, each on their own copy, and send their pieces to a shared one. Git is the tool that keeps that from turning into a mess, and it has a word for every way it can: a piece that bounces because someone got there first, two people changing the same line, someone wiping out another's work.

This game is those moments as cards. You don't need to know any of the words. The game says them, and you will have met each one by the end of your first game.

the two-minute version or play: the first game explains itself

How a day plays

  1. Write a pack

    Each day you have three ops (two on some days, four on others) and a pack of up to four commands: git add, commit, pull and push, and the cards in your hand, blame, revert, push --force and reflog.

  2. The day closes

    Everyone's packs run against the shared main together, in a random order. Push after someone else got there first, without pulling, and you're rejected, in Git's own words.

  3. Ship v1.0

    When main is long enough, someone tags v1.0 and CI flips every commit face-up. The most clean lines wins, unless four bugs reach production: then it's down, and the least blamed wins.

Why play it

Questions

Do I need to know Git?

No. Your first game walks you through a day, and every command says what it did. If you do know Git, it's all accurate.

Is it free?

Yes: no account, no ads, nothing to buy.

How long is a game?

Twelve days of 60 seconds or 5 minutes, or seven days of 24 hours. A day ends early once every pack is in, and the game ends as soon as someone ships v1.0.

How many players?

Two to five: you and the bot, or a room of friends, with bots in any seats left over.

Is it finished?

It's a beta, and the beta is the playtest: the rules are at v0.2 and will change with what people say. Every game ends with a box for telling us how it went.

Is it open source?

Yes, under the AGPL-3.0, on GitHub. Much of it was written with AI and reviewed by people; here's how.

One tap to a game

play now