It Runs DOOM. Now It Runs on GitHub.
We’ve all heard the rule:
If it can run DOOM, it’s a real computer.
Over the years, we’ve seen DOOM running on pregnancy tests, tractors, ATMs, and digital cameras.
But one day, while staring at those little green squares on my GitHub contribution graph, a dangerous thought crossed my mind:
Why are they just sitting there?
What if… they did something?
The Goal
I’m officially starting an experiment to render DOOM directly onto the GitHub Contribution Graph.
Yes, the exact 7×52 grid that tracks your commits.
This is not a joke project.
This is not a useful project.
This is a “should-not-exist-but-now-it-must” project.
The Vision
Here’s the plan (at least, the current version of it):
- Extract raw DOOM gameplay frames
- Downsample each frame to a 7×52 resolution (the contribution grid size)
- Map grayscale pixels to GitHub’s 4 shades of green
- Use
git commit --dateto paint frames into history - Let the contribution graph become a display
If this works, your GitHub profile becomes a DOOM renderer.
The “Impossible” Challenges
This isn’t just a script — it’s a fight against reality.
1. The Refresh Rate
GitHub doesn’t update contribution graphs instantly.
- How slow is it really?
- Can it be tricked into pseudo-animation?
- Is DOOM at 0.1 FPS still DOOM?
2. The Commit Explosion
- Will GitHub rate-limit commits?
- Will my profile get flagged?
- What happens if I make 10,000 commits in 5 minutes?
(We are about to find out.)
3. The Input Problem
This is the wild part:
- Can git pushes control movement?
- Can branch names represent actions?
- Can DOOM be played using version control?
I don’t know yet.
And that’s the fun.
This experiment will probably:
- Break things
- Confuse recruiters
- Permanently ruin a GitHub profile
Worth it.
Join the Chaos
I need help from:
- Git wizards
- DOOM enthusiasts
- People who enjoy unnecessary technical suffering
If this idea made you smile, cringe, or question my sanity — that’s a sign.
This is Day 1 of the GitHub DOOM experiment.
Let’s see how far green squares can be pushed.
If it runs DOOM… it deserves to exist.
Top comments (4)
For this (at least the Doom side), I'd recommend using the Doom engine source (here) and replacing the render code with a C sourceport of gitfiti. I also voulnteer to use my Doom licensce for this. When the code and whatnot are finished, I can, you know, play it.
This is 100% an ai generated post.
First of all, the refresh rate would be a year per frame.
A contribution graph goes from Jan-Jan (next year), so it would take a year to load the next frame.
Also, if I'm just misinterpreting this and you are just using the UI, but modifying the JS, then it might be possible, but again, as you said, the refresh rate would suck.
Kudos to @gamelord2011 for actually taking this seriously
hey, man. At least you're not trying to train an AI, but have to sift through the data by hand to not get sued...
Bro is running doom on github😭