> For the complete documentation index, see [llms.txt](https://docs.getdot.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getdot.ai/train-dot/version-control.md).

# Version Control

Dot can sync the files it manages — notes, table documentation, relationships, custom skills, and dashboards — with a Git repository. Pick the provider you already use:

* [**GitHub**](/train-dot/version-control/github.md) — install the Dot Context Sync GitHub App and pick a repo. Webhooks are auto-created for you.
* [**GitLab**](/train-dot/version-control/gitlab.md) — paste a Personal Access Token (gitlab.com or self-hosted). Webhook is set up manually with a URL and secret Dot displays for you.

You can connect both providers at the same time — every change in Dot fans out to all configured repos in parallel, and webhook events from any provider pull changes back into Dot.

## Why version-control your context

Your context lives in plain Markdown and YAML files. Keeping it in Git gives you:

* **Audit trail** — every change is a commit. `git blame` shows who changed which note and why.
* **Backup + disaster recovery** — restore an accidentally deleted note with `git revert`, or rebuild a fresh server from the repo.
* **AI/coding-agent interop** — Claude Code, Cursor, and GitHub Copilot can read and contribute to the same context Dot uses.
* **Code review** — important notes and skills go through PR review before reaching production.
* **Cross-environment promotion** — point staging at `dev` and prod at `main` of the same repo, then promote with a PR.
* **Bulk edits in your editor** — power users grep/sed across hundreds of notes locally, push, and Dot picks up the changes.

## What gets synced

```
notes/
├── active/          # Active notes
└── inactive/        # Archived notes

data_sources/
├── active/          # Active table documentation
└── inactive/        # Archived table documentation

relationships.yaml   # Table relationships
apps/                # Dashboards as code (.app sources + .app.lock)
skills/              # Custom skills
```

All files use Markdown (`.md`) with YAML frontmatter, or plain YAML.

{% hint style="info" %}
Only context files are synced. Database connections, user accounts, chat history, schedules, and billing settings stay in Dot.
{% endhint %}

## Version history and undo

You don't need a Git provider to get history and undo. Every change to your context is a commit, and Dot keeps that history for you whether or not you've connected GitHub or GitLab.

Open Version History from the sidebar to see the full list of changes, each with a diff. From there you can roll the whole model back to an earlier point. You can also undo a single thing: open a table on the Model page, look at its history, and revert just that table if something went wrong. Reverting doesn't erase anything. Dot records the undo as a new change, so you can always see what happened and when.

Reverting is an admin action by default. Admins can let modelers do it too with the "Can revert version history to a previous commit" permission, under Settings, then Advanced Settings, then Modeler Permissions.

## Workspaces

Each org and each workspace has its own independent connection — switching to a workspace shows the empty Connect panel even if the parent org is connected. This lets you keep separate workspaces pointing at separate repos (or no repo at all).