> For the complete documentation index, see [llms.txt](https://doc.realvirtual.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.realvirtual.io/basics/revision-management.md).

# Revision management

Controlling your development

realvirtual.io (Unity) projects can be controlled by a revision management system. A revision management system is providing several big advantages:

* You always know how has changed what in your project
* You can always step back to all versions of your project
* You can separate developments into different branches
* You can merge branches back into your main branch

A revision management is very usefull when you are working on big projects with a bigger team.

There are several revision management systems available which can work with Unity. For example you could work with [Subversion](https://subversion.apache.org) or [GIT](https://git-scm.com). Even if GIT is in very widely used in IT development, our experience is, that Plastic SCM is the best working revision management system.

Plastic SCM was acquired by Unity some time ago and is very well integrated into Unity. On our point of view it is much easier to use than GIT.

<figure><img src="https://260262196-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpYxFg97YnJX96UzNNTSd%2Fuploads%2Fgit-blob-20a8003df701b0f5953a8da7c640b3ba050205a8%2Frevision-plastic.png?alt=media" alt=""><figcaption><p>Plastic SCM</p></figcaption></figure>

Please check the Plastic SCM Website for more information about plastic.

{% embed url="<https://www.plasticscm.com>" %}

{% embed url="<https://docs.unity3d.com/Manual/PlasticSCMPlugin.html>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.realvirtual.io/basics/revision-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.