> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/learn/review-workflow/pull-request-comments.md).

# Pull request comments

Get the latest Argos build status and a link to the build page posted automatically on your GitHub pull requests.

Argos posts a comment on your GitHub pull requests with the latest build results, so your team sees visual changes without leaving the PR.

Every time a build status updates, Argos updates the comment with the latest status and a link to the build page.

{% hint style="info" %}
Pull request comments are available on GitHub. On GitLab, Argos reports results through [commit statuses](/docs/learn/review-workflow/summary-checks.md) instead.
{% endhint %}

![Argos GitHub pull request comment](https://content.gitbook.com/content/0slCNmeVzY3qdh0I85HX/blobs/5vmJOkAEzxrqgbuhPJVX/github%20pr%20comment%2054bebb73962dc705b32c33f577fb9dd0.png)

### What the comment shows

For each build, the comment lists its status, a link to inspect it, and a **Details** column that summarizes the changes — for example `2 added` or `4 changed, 3 ignored`. [Ignored screenshots](/docs/learn/reliability-and-flakiness/flaky-test-detection.md#ignore-changes) are counted here too, so you can see at a glance how much was filtered out as noise.

If you [deploy with Argos](/docs/learn/deployments.md), the comment also lists your deployments with their preview URLs.

### Silence pull request comments

To stop the Argos bot from commenting on your pull requests:

1. Go to your project **Settings** in Argos.
2. In the **Connected Git Repository** section, uncheck **Enable pull request comments**.
3. Save the settings.

Argos stops posting build status updates on your pull requests. Re-enable the checkbox at any time to turn them back on.


---

# 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://argos-ci.com/docs/learn/review-workflow/pull-request-comments.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.