> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/version-control/revision-history.md).

# Revision History

If a project is under version control, the revision history table shows all activity for that project, including user, check-in date, revision notes, and status. To see the revision history for a project, do the following:

1. Click on the project name in the project list and click the *Revisions* tab to view the revision history. The system displays the active revision n bold. NOTE: This may or may not be the latest revision.
2. Click ***Edit*** to update revision status or revision notes.
   * select revision status from *Draft, Beta, Released*
   * added for Release 8.3 are *Discontinued*, *Restricted* (*Restricted* only available to Designer Users with admin access)
3. Click ***Revert*** to update to a later version (not shown) or revert to a prior version.
   * Designer Users with read-only access will not be able to revert or edit revision notes (Release 8.3+)

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-4275a95acaf670ffd15253a9405bc7490e6fdc60%2Ff1311822-53b2-4bad-a647-81fb4e19bc2b.png?alt=media)

For v8.2 the revision history displays two additional pieces of meta data, as follows:

* When the project is checked out, the revision history shows the check-out details (see A below) including:
  * Who checked out the project and when
  * On which installation the checkout occurred
  * In which Designer workspace the checkout occurred
  * The local project ID, which is the unique identifier for the checked out project and used on the server
* Revisions show from which revision the changes are based (see B below). This is normally sequential; for example, revision 3 is based on revision 2 and revision 2 is based on revision 1. However, this meta data allows you to create "branches" and still see the prior source for any revision and trace the revision journey.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-0b6a9cbd322ca6df02843f55c90f1828bf5b2524%2F1afd8590-bb48-49fd-a12e-554d25871ba3.png?alt=media)


---

# 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://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/version-control/revision-history.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.