How pomdap/gb-studio-ci works
Project type and purpose
• This is a CI‐centric open-source tool: a Docker image (“GB Studio CI”) pre-packaged with GB Studio CLI and related utilities.
• Its purpose is to simplify and standardize the export of GB Studio games in a GitHub Actions pipeline.
File structure
• Top-level files:
• Dockerfile – defines how the CI image is built (base OS, installs GB Studio CLI, dependencies).
• package.json – likely used to pin versions of CLI/tools or manage ancillary scripts.
• README.md, LICENSE – documentation and licensing.
• .github/workflows – multiple YAML files that drive:
• building and publishing the Docker image (build-container-image.yml)
• validating new images (check-container-image.yml)
• reacting to upstream GB Studio releases (check-gbstudio-release.yml)
• housekeeping old workflow runs (clean-workflow-runs.yml)
• .vscode – editor configs (not critical to runtime architecture).
README for additional insights
• Confirms:
• Supported image tags map to GB Studio versions.
• Typical usage is as a container in a GitHub Actions job where you mount your GB Studio project, invoke gb-studio-cli make:rom, then upload artifacts.
• Provides example workflow snippet illustrating container usage, checkout, CLI call, and artifact upload.