> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/create-content/version-control.md).
# Version control
You can monitor all the changes people have made to your content using to the **Version history** side panel.
### Version history
In the Version history of a section, you can see a list of all the actions that changed the content within it. These include:
* When someone made live edits to the section.
* When someone merged a change request.
* When someone performed a Git Sync operation.
### View historical versions of content
To view past versions of your content and see the changes that were made, click the **Version history** button in the section header, or open the **Action menu** next to the section or change request title and click **Version history**.
Click on any item in the list to see how your content looked at the point this change was made. This is very similar to how you view change requests.
### Show changes
When you are viewing an old version of your content, you can choose to highlight the differences between the old and current content — similar to diff view in a change request.
To enable or disable this, use the **Show changes** toggle at the bottom of the **Version history** side panel.
With show changes enabled, content that has changed will be highlighted by an icon on the left of its content block.
### Viewing historical published versions
If you're investigating the version history of a published section, you can also view previews of what the previous versions looked like in the published context (i.e. what the end user would see).
You can do this by:
{% stepper %}
{% step %}
From the version history side panel, select the revision
{% endstep %}
{% step %}
Copy the ID at the end of the URL
{% endstep %}
{% step %}
Add it at the end of your published docs URL as `/~/revisions/`
{% endstep %}
{% endstepper %}
### Roll back to a previous version
Rolling back allows you to revert a section's content to the way it was at a previous point in time. This is helpful if you've accidentally made a breaking change or deleted content and need to quickly get back to a previous version of the section.
To roll back to a previous version of your section, hover over the version in the side panel, click the **Actions button** and click **Rollback**.
---
# 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://gitbook.com/docs/create-content/version-control.md?ask=&goal=
```
`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.