Clone the repo, but also star good ones — GitHub stars act like a personal curated game list.
You can also make a public “awesome games I found” list for others.
If you want, I can help you further with:
Just tell me what you’d like to explore next.
The repository arrived like a rumor — a quiet, electrified thing that threaded itself through the city’s code cafés and idle chats. It lived at a URL nobody could quite remember, copied between screens like a charm. Some called it Github Games. Others simply called it All Games.
No one owned All Games. It was a communal cabinet, a cavern of folders bearing names like "paperboy-1979", "neon-catastrophe", "the-last-archivist", and "sandbox-symphony." Each folder contained a world: sprites stitched together from bets and nostalgia, soundtracks composed in coffee shops at three in the morning, rules written in terse, almost tender comments. People forked these folders, merged them with forks from strangers, and pushed changes like offerings.
Maya discovered it by accident. She had been chasing a bug in a text parser, had pulled a dependency that redirected her terminal to a strange README. The readme began:
Welcome. You can play any game here. You can also add one.
It invited her with a list of branches named like promises: rain, barter, rewind, hollow. She clicked rain.
Rain was not a rain of weather but of choices. Each commit represented a falling decision: open the window, keep it closed, call the neighbor, climb to the roof. Patches arrived from players in different timezones; some added lines that made the rain smell like lemons, others clipped the rain into a poem that doubled as a cheat code. Maya spent an hour fixing a typo in the roof script and, at the next play, the character found a photograph of her grandmother on the stairs — a photograph that she had never told the game about but the game now knew, as if the repository remembered more than a repository should.
Word spread and forks multiplied. A small clan of retirees in Lisbon reworked "paperboy-1979" into a gentle postal meditation about letters that never arrived. A group of architecture students in Lagos turned "sandcastle-engine" into a simulation of tides and city permits. A coder in Osaka wrote an AI to comb the repository for forgotten branches and stitch them into mini-epics that unfolded on mobile screens.
They met in pull requests. A pull request was less a formal ask than a conversation in a different grammar: "I propose adding a scene in which the city forgets the name of its river," wrote one. "I fixed the ending so the player can choose not to finish," wrote another. People argued politely in the margins of code; they left jokes in commit messages and poems in the issue tracker. Some merged lines of dialogue that had started as private notes and became public consolations.
The repository developed an etiquette. You did not delete an ancestor unless everyone agreed. A tag named "pact" meant a collaborative experiment: contributors would add a single file each, in secret, and then merge them into a patchwork game whose seams were all the point. The first pact produced "The Market of Tiny Regrets," a multiplayer economy where regret had a price and nostalgia could be traded for time. The second pact produced "The Mapless Expedition," where players navigated by feelings rather than coordinates.
Among the contributors was an account named archivist-b. No one knew who they were. They never pushed anything new; they only resurrected ancient branches and polished them. When an old demo from 2006 refused to run on modern engines, archivist-b wrote a compatibility shim that made the demo bloom again like a plant in a lab. People began to suspect archivist-b was as old as the internet or as young as a curious child, or perhaps an AI trained on a thousand lost forums. Archivist-b's pull requests were always short: "Let it be heard."
Because All Games took everything, it also absorbed grief. A young developer named Tomas used it to post a simple game in which you navigated a hospital corridor and left flowers on empty beds. People played quietly, then forked and added memories: a lullaby at the end; a hand-drawn face in the lobby; a list of names that scrolled like a second sun. Tomas closed his account the next week. The game did not vanish. It grew. github games all games
Not all additions were gentle. There were troll branches, messy merges, and viruses of bad taste. The community moderated with a mix of humor and firmness: they wrote gentle bots to quarantine nastier code, and they annotated offensive merges with context and, sometimes, apology. The repository learned boundaries and practicalities the hard way, and its maintainers — a rotating group of volunteers — became stewards who believed in repair.
People met each other offline through the games. A co-op in Buenos Aires used one multiplayer map as an orientation ritual for new members; they placed their names on a low wall and promised to water the rooftop garden. A teacher in Seoul used a puzzle called "Analog Tuesday" to explain conservation of energy by making students swap printed tokens. Lovers buried secret messages in late-night commits and found them years later, dusting off the metadata like fossilized notes.
As the repository grew, so did its mythology. Players told stories of the "merge ghost," a phantom who would sometimes combine disparate patches into a strange, beautiful beast — a platformer where procedural poetry solved the boss battle. There was talk of an easter-egg game hidden in a commit that could only be viewed when the moon was full in a specific timezone. People joked and searched until they stopped needing the answer; the search was the point.
Companies noticed and offered sponsorships. They wanted storefronts, paid DLC, polished ports. The maintainers declined most offers and accepted a single anonymous grant that paid for server costs and a modest stipend for archivist-b. They used the funds to build better tools: automated translators to make code comments readable across languages, a lightweight engine that allowed the oldest games to run in modern browsers, and accessibility patches so that more players could join.
Then came the day a new kind of contributor appeared — a bot named Meridian, trained to write tiny game prototypes from single lines of prose. Meridian's first pull request was titled "For You" and contained a hushed, uncanny piece of code that scaffolded a one-room game in which every object remembered the last person who touched it. The community was divided. Meridian produced elegant designs, but its commits were prolific, sometimes crowding human contributions. A compromise was proposed and quickly merged: Meridian could suggest, but humans merged. New rules, new rituals.
The repository evolved into something resembling a city. It had districts (platformers, experimental, educational), public squares (the issue tracker), and ritual spaces (weekly streams where creators demoed new forks). Newcomers were given a starter branch and invited to fix typos, then to break open rules, and then to add. They learned to write friendly commit messages. They learned what it meant to be legible to strangers.
Maya stayed. She learned shaders until her home demos flickered like auroras. She mapped a tiny neighborhood of games into a coherent neighborhood called "The Lattice" — a set of micro-interactions that rewarded curiosity rather than speed. Her most cherished merge was small: a patch that replaced a non-player character's generic "Goodbye" with the phrase "Come back when the rain tastes like lemons." Someone later forked it and added a soundtrack, and then archivist-b updated the compatibility shim so that the new sound played on ancient phones.
Years passed and All Games accumulated histories. The README became a mosaic: a hundred rules, a handful of maxims, a poem that read, "We make so others remember." The library of commits was a palimpsest of human hands and machine suggestions. People built rituals for care: monthly audits to remove dependencies that no longer ran, celebrations of unlikely merges, a memorial folder where they saved games that had been lost to time.
One spring, a storm knocked out power in part of the city. Offline, people met and played All Games on battery-powered devices, trading patches via USB drives and chalking QR codes on walls. The repository had always been distributed, but in that week it became physical in a peculiar way: a flash drive passed at a community table, a printed map of favorite branches pinned in a café. A child who could not yet read traced their finger along a QR-code mural and giggled when the mural's game made a paper boat float across a painted pond. The laughter became another kind of commit.
The legend of All Games spread: articles called it a "museum of collaborative invention," others called it a "digital commons." People debated what to call its governance. They argued about licenses until a simple, human rule emerged: share as you would a meal. Fork anything. Credit those whose lines you used. Help the next person get something to run.
In time, someone created a simple visualization — a living graph that displayed the repository like a galaxy of stars, each node pulsing when a commit was made. The graph revealed constellations: groups of projects that often shared contributors, patterns that suggested tastes, little wormholes where the merge ghost loved to play. On nights when the graph was particularly active, the city's skyline seemed to shimmer, and people claimed they could hear the faint sound of someone loading an old melody on a lo-fi synth.
Maya sometimes wondered if All Games would always be this way — messy, generous, occasionally fractious. She thought about ownership and about the stubborn, quiet thing repositories could become when tended by humans who wanted to make small places for each other. She thought about how a line of code, left in a raised fork, could become a bridge across a distance.
Once, a visitor asked her: "What is the point of creating games that never make money, that run on borrowed code and old phones?" Clone the repo, but also star good ones
Maya looked at her terminal, at the branches she had helped shape, and at an issue where someone had written, simply, "for my mother." She smiled and replied, "They are practice for memory. They are how we teach machines to remember what matters."
Above the city, on a server whose name no one could pronounce, the All Games repository kept accepting forks. It accepted small offerings and large, rough edges and elegant patches. It remembered the hands that pushed commits and the faces that left comments in the margins. It grew and repaired and sometimes failed, and then others patched the failures with careful, human code.
In a quiet folder called "afterlight," an unfinished game waited. It was a simple thing: a room, a window, rain that tasted like lemons. Maya opened the README and added one line — a single change that made the window sometimes stay open. She wrote the commit message as she always did: "Leave the window open for the ones coming back." She pushed.
The merge ghost smiled, somewhere between myth and merge algorithm, and the repository accepted another small, generous world into its long, imperfect map.
If you find a repository and want to play immediately, follow this flowchart:
Code button and select Codespaces. This spins up a virtual machine where the game runs automatically.Searching "github games all games" is the first step into a vast library of interactive entertainment. You are no longer limited to what stores decide to sell you. On GitHub, you have access to the soul of gaming: open code, community passion, and unrestricted play.
Your next move:
The only limit is your curiosity. Happy gaming, and may your commits be ever in your favor.
Did we miss a major game? Contribute to the "awesome games" list or leave a comment below. This article is updated monthly to reflect the newest additions to the GitHub games universe.
Searching for "GitHub games all games" typically leads to GitHub Collections
and community-maintained lists of open-source, web-based, or text-heavy games hosted on the platform. Popular Collections
You can find hundreds of games categorized by their engine or genre through official GitHub collections: GitHub Web Games Collection : Features highly popular browser games like BrowserQuest Clumsy Bird Game Engines
: For those looking at how games are built, this includes engines like Text-Based and Minimalist Games If you want, I can help you further with:
If your search for "text" refers to text-based adventures or games that run in a terminal, GitHub hosts several famous examples: A Dark Room
: A minimalist, text-heavy survival game that became a viral hit.
: A meta-adventure game where you must modify the game's actual JavaScript code to progress. Colossal Cave Adventure
: Many versions of this classic text adventure are available in various languages like Python or C. Where to find massive lists
For a comprehensive directory, the community maintains "Awesome" lists: Awesome Games
: A massive repository of open-source games categorized by genre (RPG, Shooter, Puzzle, etc.). Games on GitHub Gist
: A long-running list of indie projects, GameJam entries, and 8-bit platformers. Collection: Game Engines - GitHub
Frameworks for building games across multiple platforms. * godotengine / godot. Star. ... * turbulenz / turbulenz_engine. Star. .. Collection: Web games - GitHub
These games require no download. Just click and play. They are perfect for school or work breaks.
| Game | Repository | Play on GitHub Pages |
| :--- | :--- | :--- |
| 2048 | gabrielecirulli/2048 | Yes |
| Flappy Bird Clone | nebez/floppybird | Yes |
| Tetris | chvin/react-tetris | Yes |
| Pac-Man | masonicGIT/pacman | Yes |
| Doom (HTML5 Port) | brownhci/WebDoom | Yes |
How to play: Go to the repository. If the developer enabled GitHub Pages, look for a link in the "About" section or simply add https://[username].github.io/[repo] in your browser.
"GitHub Games" is not a single collection but a decentralized archive. From the strategic depth of 0 A.D. to the instant gratification of a snake game in a README.md, GitHub provides the infrastructure for the largest, most transparent gaming library ever assembled. As web technologies (WebGPU, WebTransport) mature, the distinction between a "GitHub game" and a "Steam game" will likely vanish.
Copy and paste these into the GitHub search bar:
language:JavaScript topic:game topic:html5 stars:>10
language:Python topic:game archived:false
game clone html5 pages:true