GitHub permissions

GitHub is optional. Sign-in, source access, test-file synchronization, and issue or pull-request actions have different purposes.

Identity and repositories

GitHub sign-in identifies your user account. It does not automatically grant TestVibe access to every repository or give other users access to your TestVibe workspace.

In Settings → Repositories, connect the source repository you want TestVibe to read. Install or configure the GitHub App for the intended organization and repositories. Repository metadata and content access lets TestVibe inspect the app's source and changes.

Test-file synchronization is a separate setting in Repositories. Review its destination, branch, and synchronization behavior before enabling it. Repository-changing actions need the appropriate write permission; reading source does not imply that a proposed change has been applied.

Organization and integration access

Organization team synchronization needs permission to read organization members and teams. Repository installation access alone may not provide that permission.

Issue and pull-request features also depend on the permissions and connector configuration for the selected target. An administrator may need to approve an updated GitHub App permission request before a newly enabled feature works.

When access fails, check the selected GitHub account, installation, repository selection, organization policy, and requested permission. Do not solve a missing repository by granting unrelated access.

See connect GitHub, repository settings, and connection troubleshooting.