# Choose a repository

The repository is the center of a TestVibe workspace. It is where TestVibe reads test definitions, writes generated files, stores project settings, and starts GitHub Actions workflows.

Choose the repository that should own the testing setup.

## What To Choose

| Repository choice            | Use it when                                                                 |
| ---------------------------- | --------------------------------------------------------------------------- |
| Application repository       | Your team wants tests, workflows, and generated files beside the app code.  |
| Dedicated testing repository | Your team wants UI testing assets separate from the application repository. |
| Existing TestVibe repository | The repository already contains TestVibe setup or generated tests.          |
| New repository               | You want TestVibe to initialize a clean testing project.                    |

The right choice is the repository your team expects to review, maintain, and run tests from.

## Repository Selection Flow

Depending on your GitHub access, TestVibe may ask you to select:

1. A GitHub App installation.
2. A team or organization context.
3. A repository.

If there is only one valid option, TestVibe may skip a selection screen.

## Before You Select

Check these details:

| Check             | Why it matters                                                                    |
| ----------------- | --------------------------------------------------------------------------------- |
| Repository access | Your GitHub account needs access to the repository.                               |
| App installation  | The TestVibe GitHub App must be installed for the repository.                     |
| Team context      | Organization repositories may appear under a team selection.                      |
| Test ownership    | The selected repository is where generated files and workflows will live.         |
| Target site       | The repository should be associated with the app or environment you want to test. |

## If The Repository Is Missing

Common reasons include:

* the TestVibe GitHub App is not installed for that repository
* the repository was not selected in the GitHub App installation
* you selected the wrong installation or team
* your GitHub user does not have repository access
* GitHub access was just changed and TestVibe needs a refresh

See [Missing repositories](/troubleshooting/missing-repositories.md) for recovery steps.

## Next

After choosing a repository, either [Create a new project](/workspace/create-new-project.md) or [Connect an existing project](/workspace/connect-existing-project.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testvibe.com/workspace/choose-repository.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.