Connect GitHub to your Goodspeed app
Generated apps live in private GitHub repositories under your own account or org. Six pre-wired Actions workflows run CI, E2E, security, visual regression, crash-rate monitoring, and translation checks automatically. Goodspeed wires GitHub into every app that needs it at generation time, so you start with a working integration, not a blank config and a documentation tab.
WHAT GETS WIRED IN
Built into every GitHub build
Every app Goodspeed generates with GitHub includes these wired integrations from the first build. No manual setup required.
| Item | Description | Strength |
|---|---|---|
| Repository created under your own GitHub account or org via a personal access token with repo scope. Goodspeed never owns the repo. | Repository created under your own GitHub account or org via a personal access token with repo scope. Goodspeed never owns the repo. | 01 |
| ci.yml runs tsc --noEmit, Jest unit tests with coverage, and ESLint on every pull request; merge is blocked until all three pass | ci.yml runs tsc --noEmit, Jest unit tests with coverage, and ESLint on every pull request; merge is blocked until all three pass | 02 |
| e2e.yml runs the Maestro end-to-end suite against a development build on every PR targeting main, covering the core user flows defined in .maestro/ | e2e.yml runs the Maestro end-to-end suite against a development build on every PR targeting main, covering the core user flows defined in .maestro/ | 03 |
| security.yml runs pnpm audit at high severity and a Semgrep scan on every PR; fails the check on any high-severity vulnerability in the generated dependency tree | security.yml runs pnpm audit at high severity and a Semgrep scan on every PR; fails the check on any high-severity vulnerability in the generated dependency tree | 04 |
| visual.yml captures screenshots of key screens with Maestro and diffs them against baselines stored in the repo, flagging visual regressions as a required PR check | visual.yml captures screenshots of key screens with Maestro and diffs them against baselines stored in the repo, flagging visual regressions as a required PR check | 05 |
| crash-free.yml polls Sentry after a production EAS Submit and alerts the team if the crash-free session rate drops below the configured threshold (default 99.5%) | crash-free.yml polls Sentry after a production EAS Submit and alerts the team if the crash-free session rate drops below the configured threshold (default 99.5%) | 06 |
| i18n.yml compares every locale JSON against en.json on PRs, failing if a declared locale is missing any key so translation gaps never reach users | i18n.yml compares every locale JSON against en.json on PRs, failing if a declared locale is missing any key so translation gaps never reach users | 07 |
| Trigger model: ci, e2e, security, and visual workflows trigger on pull_request targeting main; crash-free.yml triggers on workflow_run after the EAS Submit workflow completes; i18n.yml triggers on pull_request | Trigger model: ci, e2e, security, and visual workflows trigger on pull_request targeting main; crash-free.yml triggers on workflow_run after the EAS Submit workflow completes; i18n.yml triggers on pull_request | 08 |
| Workflow failure handling: a failed required check blocks the PR merge; GitHub sends an email to the committer automatically. Re-run the failed job from the Actions tab after fixing the root cause. No automatic retry is wired because silent retries can mask flaky tests. | Workflow failure handling: a failed required check blocks the PR merge; GitHub sends an email to the committer automatically. Re-run the failed job from the Actions tab after fixing the root cause. No automatic retry is wired because silent retries can mask flaky tests. | 09 |
Source: gas-template repository · source-control/ci
REAL GENERATED CODE
A snippet from a GitHub integration the pipeline ships
This pattern comes directly from the gas-template codebase. The studio generates GitHub integration code like this for every app that includes it, not a placeholder you have to fill in yourself.
BYO repo setup
// Connect your GitHub in the Deploy tab: // 1. Create a token at github.com/settings/tokens // with the 'repo' scope. // 2. Paste it into the GitHub section of Connect Accounts. // 3. Enter your username or org name as the Owner. // // On the next build Goodspeed creates a private repo // under your account and pushes the generated source. // All future builds push to the same repo; you own it. // // The 6 Actions workflows ship in .github/workflows/ // and run automatically on push and pull_request.
GDaily Allergens
Today's log
Gluten
Tree nuts
Shellfish
Dairy
HomeScanLogProfile
APPS THAT USE GITHUB
Where this integration ships
These app types include GitHub as part of the generated stack. Each link goes to a full spec page with capabilities, scored ideas, and a pipeline walkthrough.
- Build a Productivity App appProductivity apps succeed when they remove friction from the moment the user decides to work. Goodspeed generates a productivity app with Pomodoro timer, focused task queue, distraction blocker hooks,PRODUCTIVITY APP
- Build a Social App appBuilding a social app from scratch means solving hard infrastructure problems: real-time feeds, fan-out writes, notification delivery, and content moderation hooks. Goodspeed generates a complete sociSOCIAL APP