> 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/faqs.md).

# ChangeSets FAQs

Find answers to common questions about the ChangeSets feature that creates a list of PRs to be merged.

<details>

<summary>Can a single PR be part of multiple ChangeSets?</summary>

Yes, technically you can add a PR to multiple ChangeSets, but it will be merged with the first ChangeSet that is flagged for merging.

</details>

<details>

<summary>Can a single ChangeSet have multiple PRs from the same repository?</summary>

Yes, ChangeSets can have multiple PRs in the same repository. If using global CI validation, you will have to handle incorporating changes from multiple PRs/branches in the same repository yourself.

</details>

<details>

<summary>Can more PRs be added to the ChangeSet once "Start CI" is triggered?</summary>

Yes, if a new PR is added to the ChangeSet, the CI webhook will be retriggered with a new Status Run ID.

</details>

<details>

<summary>Can I review all previous the check run statuses?</summary>

Yes, the Aviator web app shows links to all previous status checks. Only the latest status run is considered when validating the ChangeSet for merge.

</details>


---

# 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/faqs.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.