GitHub Connection Issues
GitHub is an optional integration in TestVibe — projects, tests, runs, and results all live in TestVibe's cloud and never require a repository. GitHub is used for sign-in and optional connected features, each with its own scope.
Where GitHub Is Used
| Use | What TestVibe asks for |
|---|---|
| Sign in with GitHub | Identity only — your account and verified email. No repository permissions. |
| App Repository (optional) | Read access to one repository, so the assistant and coverage can read your app's code. |
| Test Files Sync (optional) | Write access to your target repository for the two-way test files mirror, requested only when you enable sync. |
Repository and issue integrations request their own access when connected. Plain sign-in does not request repository access.
Permission Symptoms
| Symptom | Likely cause |
|---|---|
| Repository picker is empty | Your GitHub connection has no access to the repository you expect. |
| The assistant or coverage cannot read the App Repository | Read access to that repository was not granted. |
| Test Files Sync fails to push | Write scopes were not granted, or access to the target repository was removed. |
| The wrong GitHub account is connected | You authorized a different GitHub account than the one with repository access. |
Update Access
- Open Settings → Repositories for source access or test-file sync. For issue imports and issue actions, check Settings → Connectors.
- Grant access to the specific repository TestVibe needs.
- If the repository belongs to an organization, an organization owner may need to approve the authorization.
- Return to TestVibe and refresh the picker or retry the sync.
If you do not manage the GitHub organization, ask an owner to approve access for the repository you named.