> 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/git-based-source-control/advanced/code-review/reviewers.md).
# Reviewers
## Overview
A reviewer is an individual or Team that is appointed to a pull request to provide feedback on a set of changes. They are notified by e-mail and in the *Notifications* screen of the Web App if a review has been requested from them.
## Reviewing a Pull Request
Pull requests need to be reviewed and approved before getting merged into `main`.
### Accessing an Open Pull Request
Reviewers and contributors can view open pull requests in a few ways.
The easiest gateway into viewing an open PR is to navigate to the *Notifications* screen and click on an open PR.
Another option is to navigate to the *Pull Requests* page through the main nav bar. Clicking into the *Open* part of the toggle will display open pull requests across all repositories and throughout all organizations.
The last method is to navigate to a specific repository and click on the *Pull Requests* tab. Any open PRs will be listed under the *Open* side of the toggle.
### Discussing an Open Pull Request
Both reviewers and contributors can create and engage in a dialogue about the contents of a PR.
To read or add a comment, navigate to the *Conversation* tab. Here you will see a full history of what has been discussed as it relates to the changes proposed in the PR.
{% hint style="info" %}
The *Conversation* tab serves to provide a space for discussion and feedback. Any activity that happens within it neither starts a review nor blocks the PR from being merged.
{% endhint %}
### Submitting a General Review
After reviewing all changes, you can add a general and high-level review to the PR.
Click on the *Submit Review* dropdown and enter your comments.
You can either approve, comment, or request changes using the radio selectors. If you approve the changes, the contributor can continue to [merge](/docs/git-based-source-control/advanced/merging.md) the PR into `main`. Once finished, click the *Submit* button.
{% hint style="info" %}
Although both contributors and reviewers can comment on a PR, only reviewers can approve or request changes.
{% endhint %}
### Submitting a Review with Code Commenting
If the filetype under review supports Code Commenting, you can add comments directly on the graphical display. Code Commenting will also initialize the review process.
Navigate to the *Files for Review* tab, choose an item to comment on, and write your comment. Click the *Start Review* button to submit your comment.
{% hint style="info" %}
Review the [Vendor Integrations](/docs/git-based-source-control/supported-vendors.md) section to learn what filetypes support Code Commenting.
{% endhint %}
Continue to add other comments as needed. Once you're finished with all of your comments, click the *Submit Review* button to finalize your review.
---
# 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/git-based-source-control/advanced/code-review/reviewers.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.
