GitHub App Setup
Step 2 of onboarding walks you through registering a GitHub App on your org. This is a one-time 2-minute process. After that, token refresh is fully automatic.
What you'll create
A GitHub App registered under your GitHub org (or personal account). It grants Wololo agents scoped, auditable access to the repos you select.
Steps
- Trigger setup. In the onboarding wizard, click Set up GitHub App. This opens GitHub's App creation flow using a pre-filled manifest — you just click Confirm.
- Install on repos. After creation, GitHub prompts you to install the App. Select the repos your agents will work with (you can change this later).
- Return to onboarding. GitHub redirects you back to the wizard. The private key is automatically stored in your GCP Secret Manager.
What gets stored where
| Item | Location |
|---|---|
| App ID | GCP Secret Manager (your project) |
| Private key (.pem) | GCP Secret Manager (your project) |
| Installation ID | Supabase tenant record |
| Webhook secret | GCP Secret Manager (your project) |
The private key never touches Wololo's servers. It's written directly from the GitHub API response to your GCP project's Secret Manager.
Token refresh
Agents receive 1-hour installation tokens minted from your private key. When a token expires, the platform automatically mints a fresh one. No action required from you.
Troubleshooting
- Setup page returns an error. The callback URL may be stale. Try visiting
/api/github/setupagain from the onboarding wizard. - Agents can't access a repo. Check the App's installation in GitHub Settings → Developer settings → GitHub Apps → [Your App] → Install. The repo must be in the allowed list.
- Key lost / compromised. Generate a new key in GitHub App settings, upload to Secret Manager, and delete the old version. No downtime — agents pick up the new key on next token mint.
Not set up yet?
As an interim, you can use a Personal Access Token to give agents repo access while you complete GitHub App setup.