> For the complete documentation index, see [llms.txt](https://docs.copia.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.copia.io/docs/devicelink/jobs/pull-requests.md).
# Pull Requests
## Overview
If you are not using the recommended Copia auto-commit feature, or if you want to merge change into another branch, you can merge changes for a given backup into your repository using Pull Requests.
Navigate to the *Job History* tab under the *Jobs* screen and click on the *View Details* for a given run to review the diff. You can open a PR after a backup completes.
Differences will be displayed in the lower portion of the screen for your review. If you wish to update your Project with the data from the backup, you can select the *New Pull Request* button at the top right of the screen.
When you choose to create a new PR, you will be taken to the screen below. At this point the process is similar what's outlined in the [Pull Request and Code Review](https://docs.copia.io/docs/advanced/code-review) section. Reviewers can be assigned to the PR through the *Assign Reviewers* dropdown. Once a PR is approved, changes can be merged into the repository.
---
# 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.copia.io/docs/devicelink/jobs/pull-requests.md?ask=&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.
