Add a project

What it needs

1. A public GitHub repository.
2. A progress report from its own GitHub Actions. A workflow on the default branch uploads an objdiff report as an artifact with report in its name. Projects made from dtk-template already do this. Runs from pull requests of forks don’t count.
3. At least 5% of the code decompiled.
4. The code is really there. At least half of the source files the report counts as decompiled must exist in the repository.
5. The game can be recognised. The repository contains its disc ID, serial, title ID or ROM hash, as decomp projects normally do. Windows, DOS and Switch games: choose the system below and type the game’s exact name.
6. A GitHub account at least 30 days old. Up to 3 submissions per account per day.

# .github/workflows/build.yml (the part decomp.fun reads)
on:
  push:
    branches: [main]
jobs:
  build:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        version: [GALE01]          # one entry per build of the game
    steps:
      - uses: actions/checkout@v4
      # ... build the game and write build/${{ matrix.version }}/report.json
      #     (dtk-template: ninja build/${{ matrix.version }}/report.json)
      - uses: actions/upload-artifact@v4
        with:
          name: ${{ matrix.version }}_report
          path: build/${{ matrix.version }}/report.json

If the game is already listed, your repository joins its page and is compared build to build; it takes the listing after leading by 1 percentage point for 7 days in a row (and being listed 30 days). See one listing per game.

After you’re listed

Your project gets its own page at decomp.fun/<owner>/<repo>/. It refreshes every 6 hours and whenever someone opens the page after you push new progress. Nothing else to do. Archiving the repository tags it as archived; making it private or deleting it removes it from the site automatically.

Recent submissions

Accepted Contesting Already listed Not accepted