# How to collaborate on change requests

Change requests are GitBook’s way of safely collaborating on documentation — similar to pull requests for code. They let you propose, review, and refine updates before anything goes live.

This video and guide will take you through change requests in GitBook, covering:

* Creating [change requests](/docs/collaboration/change-requests.md) to edit content
* Reviewing edits with [diff view](/docs/collaboration/change-requests/change-requests-in-a-space.md#diff-mode)
* Tracking changes in the **Changes** tab
* [Previewing changes](/docs/collaboration/change-requests/change-requests-in-a-space.md#previewing-a-change-request)
* Merging and publishing your content live

{% embed url="<https://www.youtube.com/watch?list=PLZAlnWDc6FDt4QfYCyjiMgexzTyDfDkdI&v=sU_JbCFUE7k>" %}

{% stepper %}
{% step %}

### Create a change request

Create a **change request** before editing published docs. This keeps your work separate from live content.

If you’re new to the workflow, start with [change requests](/docs/collaboration/change-requests.md).
{% endstep %}

{% step %}

### Make and review edits

Edit content inside the change request, like you normally would. Use [**comments**](/docs/collaboration/comments.md) to leave feedback and collaborate in-context.
{% endstep %}

{% step %}

### Track changes and preview

Open the **Changes** tab (aka [diff view](/docs/collaboration/change-requests/change-requests-in-a-space.md#diff-mode)) to review what’s been modified.

Use [**Preview**](/docs/collaboration/change-requests/change-requests-in-a-space.md#previewing-a-change-request) to see exactly what will ship after merge.
{% endstep %}

{% step %}

### Request reviews (optional)

[Request a review](/docs/collaboration/change-requests/change-requests-in-a-space.md#request-a-review-on-a-change-request) when you need another set of eyes. This keeps the workflow clear and encourages discussion before publishing.

If you don’t tag reviewers, everyone with reviewer permissions in the space gets a notification. If the space has no reviewers, GitBook notifies the next role above reviewer instead.

If you need tighter controls, combine reviews with [merge rules](/docs/collaboration/merge-rules.md).
{% endstep %}

{% step %}

### Merge when ready

When everything looks good, click **Merge**. Your changes will go live immediately.
{% endstep %}

{% step %}

### Use merge rules (optional)

Set up **merge rules** to define what must happen before merge. For example, require one or more reviews for approval-heavy teams.
{% endstep %}
{% endstepper %}


---

# Agent Instructions: 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://gitbook.com/docs/guides/editing-and-publishing-documentation/how-to-collaborate-on-change-requests.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.