How pomdap/gb-studio-ci-example works
Project type and purpose
• This is not a user-facing application but a CI/CD template repository for GB Studio game projects.
• It provides a set of GitHub Actions workflows and utilities to automate building GB Studio games (ROMs, web builds, Pocket builds) and deploying them to GitHub Releases or itch.io.
File structure
• Top-level folders:
– .github/workflows: Contains all the CI workflows (main-branch CI, itchio-release, github-release, plus utility workflows).
– assets/: A library of game assets (avatars, backgrounds, fonts, music, etc.) for use in the GB Studio project.
– plugins/: A place to add GB Studio plugins.
– project/: The actual GB Studio project files (.gbsres resources, .gbsproj project file, sprites, scenes, variables).
• Config files:
– README.md: Explains usage and architecture.
– .gitignore, LICENSE, etc.
• The workflows folder contains three “entrypoint” workflows and three utility workflows:
– ci-main-branch.yml
– ci-itchio-release.yml
– ci-github-release.yml
– utility-validate-target-list.yml
– utility-extract-project-configuration.yml
– utility-build-and-upload-artifact.yml
Key insights from the README
• Workflow triggers:
– Push/PR on default branch → main-branch CI
– Tag v* → GitHub Release & itch.io Release
• Uses a Docker image (pomdap/gb-studio-ci) to perform builds.
• Utility workflows serve as reusable building blocks for:
validate targets → extract metadata → build + upload artefacts.