GitHub Connection Issues

Fix issues with the optional GitHub integration: sign-in identity, App Repository reading, and Test Files Sync.

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 in exactly three places, 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.

If TestVibe asks for repository permissions, you are connecting an App Repository or enabling Test Files Sync — never plain sign-in.

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

1. Open the GitHub authorization prompt again from the panel you are enabling (Settings → App Repository or Settings → Test Files Sync).

2. Grant access to the specific repository TestVibe needs.

3. If the repository belongs to an organization, an organization owner may need to approve the authorization.

4. 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.

Related Help

• GitHub permissions overview

• Can't see a project

• Sign-in problems