> 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/account-settings/repository-settings.md).

# App Repository & Test Files Sync

Two settings panels connect a project to Git, and they are independent of each other. **Settings → App Repository** links the repository containing your application's own code — read-only. **Settings → Test Files Sync** mirrors this project's own test files to a repository you own — two-way. Both are optional; project content — features, generated tests, configurations, run history — always lives in TestVibe's cloud.

## App Repository (read-only)

**Settings → App Repository** connects the repository that contains the application's code, on **GitHub, GitLab, or Azure DevOps** — one active source at a time. TestVibe reads it to ground the AI while generating and debugging tests, and to map [coverage](/codebase.md) of your app's areas. TestVibe never writes to this repository, and repository permissions are requested only when you connect it — never at sign-in.

## Test Files Sync (two-way)

**Settings → Test Files Sync** mirrors this project's own test files — features, specs, and Playwright configs — to a GitHub, GitLab, or Azure DevOps repository TestVibe can write to. Edits flow both ways: changes made in the app push to the repository, and edits committed to the repository flow back into the project. TestVibe's cloud stays canonical. Write scopes are requested only when you enable sync.

These are two different corpora: the App Repository is your app's code (TestVibe reads it), while Test Files Sync carries TestVibe's own test files for this project (TestVibe writes and reads them).

## Open the panels

1. Open a project.
2. Open **Settings**.
3. Select **App Repository** or **Test Files Sync** under the Project group.

## Settings that moved

Older versions kept these on a single Source Code page. They now live in dedicated panels:

| Looking for                                            | Where it lives now                                                                                                                            |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Source repository / Git export (one Source Code panel) | Split into **Settings → App Repository** (read-only code context) and **Settings → Test Files Sync** (two-way mirror) — both described above. |
| Test site URLs                                         | **Settings → Environments** — see [Configure environments and App Repository](/workspace/configure-site-url-and-repository.md).               |
| AI agent, model, reasoning effort                      | **Settings → AI Model** — see [Choose an agent and model](/ai-generation/choose-agent-and-model.md).                                          |
| Logins, tokens, test data                              | **Settings → Variables & Secrets** — see [Add API keys and secrets](/workspace/add-api-keys-and-secrets.md).                                  |
| Browser, viewport, run presets                         | **Settings → Playwright** — see [Choose browser, viewport, and configuration](/run-tests/browser-viewport-configuration.md).                  |

## Related Help

* [Choose a source repository (optional)](/workspace/choose-repository.md)
* [Connect GitHub (optional)](/workspace/install-github-app.md)
* [CLI & API keys](/account-settings/api-keys.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/account-settings/repository-settings.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.