> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/workspace/choose-repository.md).

# Choose a Source Repository (Optional)

A source repository is the repository that contains the code of the application you are testing. It is optional — TestVibe stores all project content in its own cloud and never requires a repository, and it is never asked for during project creation itself.

When a project has one and you ask the assistant to explore your app — an on-demand action, not something that runs automatically when the project is created — it reads the code alongside the live site, which produces better-grounded feature suggestions and generated tests.

## What The Assistant Does With It

| What it reads        | How it helps                                                 |
| -------------------- | ------------------------------------------------------------ |
| Pages and navigation | Suggested features cover the flows that actually exist.      |
| Forms and validation | Generated steps anticipate required fields and error states. |
| Domain language      | Feature files use the names your app and team already use.   |

Without a source repository, the assistant still explores the live site and drafts features when asked — it just starts with less context.

## When To Provide One

| Situation                                           | Recommendation                                       |
| --------------------------------------------------- | ---------------------------------------------------- |
| Your team owns the app code on GitHub               | Provide it — the extra context is free.              |
| The app is hard to understand from the UI alone     | Provide it — code fills the gaps exploration misses. |
| You are testing a third-party or closed-source site | Skip it — exploration of the live site is enough.    |

## Where To Set It

1. When adding a project from the workspace switcher, open **Advanced settings** and fill in the optional source repository field (not offered on the very first project's single-screen create form), or
2. Open **Settings → App Repository** in an existing project and set the source repository there — the more common path, since it works for the first project too.

## Related Help

* [Create a new project](/workspace/create-new-project.md)
* [Connect GitHub (optional)](/workspace/install-github-app.md)
* [App Repository & Test Files Sync settings](/account-settings/repository-settings.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.