What the banner says
The banner shows on the app page, in Settings, Repository, and once for all affected apps on the Apps list.
Reconnect GitHub
1
Click Reconnect GitHub
Click Reconnect GitHub on the banner. From the Apps list, one reconnect repairs every app on that GitHub account.

2
Sign in with GitHub
A GitHub window opens. Sign in with a GitHub account that can see the app’s repository. Raff links only what that GitHub account can see.
3
Install the Raff GitHub app if asked
If the Raff GitHub app is no longer installed, GitHub asks you to install it. Pick the account and the repositories your apps use, and finish the install.
4
Check the result
The window closes and the dashboard says “GitHub reconnected”, with the branch it is deploying. The banner goes away.
What happens after
- Each repaired app deploys the latest commit on its branch when that differs from what it runs.
- Apps you paused, and apps paused by the spend cap, are left alone.
- After you give the Raff GitHub app access to a repository again in GitHub settings, its apps deploy their latest commit by themselves.
Do it from your tools
Reconnecting needs the dashboard, because it signs you in to GitHub. API keys cannot start it. To check an app from the API, readgithub_status from Get app service. It is empty when the link works, otherwise disconnected, suspended, no_repo_access or repo_not_found.
$APP_ID is the app’s ID from List app services or raff apps list. $RAFF_API_KEY is an API key.
Next steps
Preview pull requests
Build every pull request at its own address.
Roll back a deploy
Go back to an earlier deploy.