> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/mergequeue/concepts/changesets.md).

# ChangeSets

Read an overview of the ChangeSets feature. It allows you to create a list of PRs to be merged together, which is helpful for merging a large number of PRs.

The ChangeSets feature allows you to create a list of PRs to be merged together. This is useful if you have a large number of PRs that need to be merged together (e.g., coordinated changes to a web frontend, iOS app, and Android app). ChangeSets can group PRs within the same repository or across multiple repositories.

You can create a ChangeSet by clicking the "Create New" button on the ChangeSet page. This will create an empty ChangeSet.

Add a PR to this ChangeSet by finding the PR you want to add (search by GitHub user, or by Repository name), and click the "Add to ChangeSet" button next to it. Repeat the process to add as many PRs as you like to this ChangeSet.

To remove a PR from a ChangeSet, click the "Remove" button next to the PR name.

Once ready, you can merge the ChangeSet by clicking the "Merge" button on the page. Aviator will then validate the approvals and status checks for all the PRs in the ChangeSet and merge them together. You can optionally specify additional validation requirements that must be met before the whole ChangeSet is merged. If validation fails, the ChangeSet will be marked as failed and none of the PRs will be merged.

{% hint style="info" %}
Checkout the [<mark style="color:blue;">how-to-guide for configuring ChangeSets</mark>](/mergequeue/how-to-guides/configuring-changesets.md) in your repository.
{% endhint %}


---

# 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://docs.aviator.co/mergequeue/concepts/changesets.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.