> For the complete documentation index, see [llms.txt](https://docs.coherence.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coherence.io/2.3/manual/advanced-topics/team-workflows/version-control-integration.md).

# Version control best practices

If you're using a VCS (which we highly recommend you to) like git, Subversion or PlasticSCM, here's a few tips.

* Follow general-purpose ignore rules for Unity. For example, for git, use a `.gitignore`, like [this one](https://github.com/github/gitignore/blob/main/Unity.gitignore).
* You might or might not want to version `Assets/coherence/baked`. Your call. If you don't version this folder, other developers (or your CI environment) will have to bake before the project is usable. Versioning it gets you on a ready-to-build project, but it comes at a price — a lot of noise on commits.
* Version `Assets/coherence/baked_stubs` if you're using [command extensions](/2.3/manual/networking-state-changes/commands.md). This folder contains safe fallbacks. If this folder is not versioned, you might face compilation error deadlocks that can only be solved by commenting out any usage of command extensions in your code.
* Version `Assets/coherence/Gathered.schema`. **Treat it as a binary**.

{% hint style="info" %}
Each VCS has different mechanisms to treat files as binaries. Read the documentation of your VCS of choice to learn how to set this up.

For git, add this line to your [.gitattributes](https://git-scm.com/docs/gitattributes) (create one in the root of your git repo if it doesn't exists):

```
Assets/coherence/Gathered.schema -merge -text
```

{% endhint %}


---

# 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:

```
GET https://docs.coherence.io/2.3/manual/advanced-topics/team-workflows/version-control-integration.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.