#Submitting your game

Every game is reviewed before it goes live on arcade.gamesight.io. Anthony Kinson or Robert Syvarth has to approve it. That's the one hard rule, and it applies whether you wrote the game yourself or an AI wrote it for you.

Review happens on a GitHub pull request, so you need a GitHub account and access to the repo. There's no way to submit without one; if you don't have access yet, jump to getting access and start there.

#Before you submit

Run this and fix anything it prints. It's the same check CI runs, and the fastest way to avoid a round-trip:

npm run validate

Then have a quick look yourself:

  • The game plays at http://localhost:8002/games/<your-slug>/ after npm run build && npm run preview.
  • game.json has a real description, your name in authors, and a genre.
  • Everything you changed is inside games/<your-slug>/. If you touched anything else, say why in the pull request.

#If you use Git and GitHub

Work on a branch named after your game, then open a pull request against main:

git checkout -b game/my-game
git add games/my-game
git commit -m "Add My Game"
git push -u origin game/my-game

Open the PR from the link GitHub prints, or with gh pr create --fill. Then request a review from Anthony Kinson or Robert Syvarth.

game/<slug> is a convention, not something the tooling enforces. It just makes it obvious what a branch is for. Branches live in the Gamesight org repo, so you don't need a fork.

#If you've never used GitHub

You still open a pull request. You just do it with buttons instead of commands.

  1. Install GitHub Desktop and sign in with the account from getting access.
  2. File → Clone repository, pick Gamesight/gamesight-arcade-www, and note the folder it saves to.
  3. Before you change anything, click the Current branch dropdown → New branch, and name it game/my-game. This keeps your work separate from everyone else's.
  4. Build your game in that folder (see building with AI if an assistant is doing the work).
  5. Back in GitHub Desktop, your changed files appear on the left. Write a short summary at the bottom ("Add My Game") and click Commit to game/my-game.
  6. Click Publish branch, then Preview Pull Request → Create Pull Request. That opens your browser.
  7. In the pull request, describe your game in a sentence or two and request a review from Anthony Kinson or Robert Syvarth.

If you're using an AI coding assistant that can run commands, you can also just ask it to do steps 3, 5 and 6 for you. Read what it says it's doing first, and keep the changes to your own game folder.

#Getting access

You need two things before any of the above works.

  1. A GitHub account, free, at github.com/signup. Use your Gamesight email so it's obvious who you are.
  2. Access to the repo. Message Anthony Kinson or Robert Syvarth with your GitHub username and ask to be added to Gamesight/gamesight-arcade-www. You'll get an email invitation; accept it before cloning.

You'll also need Node 24+ from nodejs.org to build and play the arcade locally. Download the LTS installer and click through it. You don't have to understand what it does, but two commands in a terminal are unavoidable if you want to see your game running before you submit it.

#What happens next

CI runs automatically on your pull request: it validates every game.json, checks achievement catalogs, and builds the whole site. A red check means something needs fixing, so click through to the log and paste the error to whoever (or whatever) is helping you.

Once Anthony or Robert approves and merges, main deploys automatically and your game is live within a few minutes.

Stuck? Troubleshooting covers the errors that come up most.

View docs/submitting-your-game.md on GitHub ↗