> 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/collaboration/change-requests.md).

# Change requests

A change request is a copy of your main content. It's based on the concept of branching, and feels familiar to anyone who uses pull requests in GitHub or merge requests in GitLab.

In a change request, you can edit, update, and delete content, request reviews on your changes, then merge them back into your main version.

To manage open change requests across your organization, see the [Change requests screen](/docs/collaboration/change-requests/change-requests-screen.md).

<figure><img src="/files/X1Yu5sAwadfJc89m6asf" alt="A GitBook screenshot showing the change requests panel"><figcaption><p>Edit your content through change requests.</p></figcaption></figure>

### Review changes in diff view <a href="#diff-mode" id="diff-mode"></a>

Open the **Changes** tab to review edits in a change request. You can review all pages in context, or focus on changed pages only.

{% hint style="info" %}
&#x20;By default, changes are shown in a "split-view". The left showing the 'before' version of the page, and the right showing the 'after' state. If you prefer to view changes inline in a single column-layout, click the diff-mode button at the top-right of the Table of contents panel.
{% endhint %}

### Create and merge a change request

{% stepper %}
{% step %}

### Open a change request

To edit content, open a change request. You can open one in a few ways:

* Click **Edit** in the top right corner of a space.
* Ask GitBook Agent to create one on your behalf.
* GitBook Agent may create one automatically when it detects a documentation gap.

If you open one manually, GitBook creates the change request and opens it in the editor.
{% endstep %}

{% step %}

### Make your changes

Edit content directly in the editor, or work with GitBook Agent.

Review your changes before you move on. You can keep editing until you're ready to request a review.
{% endstep %}

{% step %}

### Request a review

Open the **Overview** tab, then tag one or more reviewers.

Reviewers can approve your changes, leave comments, or request more edits. If you don't tag anyone, everyone with reviewer permissions in the space is notified. If the space has no reviewers, editors and admins are notified instead.

If someone requests changes, update the change request before you merge it. You can also ask GitBook Agent to review the change request.
{% endstep %}

{% step %}

### Merge

Once the change request is approved, open the **Overview** tab and click **Merge**.

GitBook applies the changes to your live docs immediately. If your space uses merge rules, GitBook checks them before merging.

Merging can't be undone. To revert or adjust content, open a new change request.
{% endstep %}
{% endstepper %}

### Working with change requests

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Change request screen</strong></td><td>View and manage change requests across your entire organization</td><td><a href="/spaces/NkEGS7hzeqa35sMXQZ4X/pages/RtzwHmNAAMW6pYmEJshK">/spaces/NkEGS7hzeqa35sMXQZ4X/pages/RtzwHmNAAMW6pYmEJshK</a></td></tr><tr><td><strong>Change requests in a space</strong></td><td>Create and review change requests in a single space</td><td><a href="/spaces/NkEGS7hzeqa35sMXQZ4X/pages/QahtV4lWA3JQnbMAvNKG">/spaces/NkEGS7hzeqa35sMXQZ4X/pages/QahtV4lWA3JQnbMAvNKG</a></td></tr></tbody></table>


---

# 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/collaboration/change-requests.md?ask=<question>&goal=<endgoal>
```

`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.