Skip to main content

Repositories

Settings → Repositories contains two independent connections: Application code and Test files. Both are optional. Project content is stored in TestVibe; connecting a repository does not make Git the project's database.

Open Settings → Repositories, see what the read-only Application code connection is for, connect a provider and repository, set up the Test files mirror with write access, check its sync state before editing in both places, and find the related settings nearby.

Application code​

Connect the repository containing the application you test, on GitHub, GitLab, or Azure DevOps. One source repository is active at a time. TestVibe reads it for Assistant context and Application coverage; this connection does not write your application code.

Repository authorization is separate from signing in. Connect the provider and select a repository that your account can access.

Test files​

Expand Set up (or Manage for an existing connection) under Test files to configure an optional two-way mirror of feature files, generated specs, and Playwright configurations. This repository needs write access. App edits push to it and repository edits can be imported back into TestVibe.

Check the sync state before editing in both places. A conflict or sync error expands this section for attention; resolve it before assuming both copies match. This connection is independent of Application code and can use a different repository.

Older screenshots may show separate App Repository and Test Files Sync settings. The current workspace layout groups them under Repositories.