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 |
|---|---|---|
| A repo on your own account | Created under your GitHub account or org through a token with repo scope. Goodspeed never owns the repository. | Delivery |
| Type check, tests and lint | ci.yml runs the type check, the unit suite with coverage, and the linter on every pull request. A merge is blocked until all three pass. | Reliability |
| End-to-end suite | e2e.yml drives the Maestro flows in .maestro/ against a development build on every pull request into main. | Reliability |
| Dependency and code scan | security.yml runs a high-severity dependency audit and a Semgrep scan, failing the check on any high-severity finding. | Reliability |
| Screenshot regression | visual.yml captures the key screens with Maestro and diffs them against committed baselines as a required check. | Reliability |
| Crash-free rate gate | crash-free.yml polls Sentry after a production submission and alerts if the crash-free session rate falls below the configured threshold, 99.5% by default. | Reliability |
| Translation completeness | i18n.yml compares every locale file against en.json on pull requests, failing when a declared locale is missing a key. | Interface |
| When each workflow fires | The check, end-to-end, security and visual workflows run on pull requests into main. The crash-free gate runs after a submission finishes. | Delivery |
| Failures block, and nothing retries | A failed required check blocks the merge and emails the committer. Re-run it from the Actions tab after a fix. Nothing retries on its own, because a silent retry hides a flaky test. | Reliability |
Source: the Goodspeed app foundation · source-control/ci
REAL GENERATED CODE
A snippet from a GitHub integration the pipeline ships
This pattern is lifted from the engineered plumbing that ships inside every Goodspeed app. 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.
Today's log
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 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 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