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

# Pull request comments

In your Account Settings, you can configure Release to add comments to your pull requests when your environments are ready.

Under the **Source Control** tab in Account Settings, find the "Pull Request Comments" option.

![](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-362cbe5bcd30837438c9cbd4bbd1e2356ff5ea78%2Fgithub-settings-2.png?alt=media)

The "Pull Request Comments" setting is turned on by default. When an environment is created from a pull request, Release will add a comment with links to the running environment.

![An example comment on a Pull Request in GitHub](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-d5331079529b2198057b02d04d2ac68a1cfe034c%2Fgithub-comment-releasehub.png?alt=media)

In the comment, the name of the application is shown (in this case, `release-blog`), followed by links to the hostnames to preview the environment.


---

# 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.release.com/integrations/source-control-integrations/github/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.