Scrolling through them feels like walking through an infinite arcade at 3 a.m. Some are polished prototypes. Others are raw passion — a single developer's attempt to recreate a childhood memory in JavaScript, or a student's first guess at a collision algorithm.

In an industry obsessed with retention metrics, battle passes, and live-service treadmills, GitHub games remind us of something we quietly lost:

A terminal-based RPG written in Bash. A puzzle game with no graphics — only emojis. A platformer whose only player is the developer's cat, via motion detection.

These games are not failures. They are artifacts of intent .

Not every game ships. Some just exist.

There’s a strange kind of poetry hidden inside GitHub repositories labeled "game" — many of which will never see a Steam page, a console launch, or even a finish line.

So here's to the abandoned game jams. The half-written READMEs. The single commit from 2016 titled "it works on my machine."

Githuball Games Here

Scrolling through them feels like walking through an infinite arcade at 3 a.m. Some are polished prototypes. Others are raw passion — a single developer's attempt to recreate a childhood memory in JavaScript, or a student's first guess at a collision algorithm.

In an industry obsessed with retention metrics, battle passes, and live-service treadmills, GitHub games remind us of something we quietly lost:

A terminal-based RPG written in Bash. A puzzle game with no graphics — only emojis. A platformer whose only player is the developer's cat, via motion detection.

These games are not failures. They are artifacts of intent .

Not every game ships. Some just exist.

There’s a strange kind of poetry hidden inside GitHub repositories labeled "game" — many of which will never see a Steam page, a console launch, or even a finish line.

So here's to the abandoned game jams. The half-written READMEs. The single commit from 2016 titled "it works on my machine."