> 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/inbox/attention-reasons.md).

# Attention Reasons

Understand the reasons for attention assignment in Inbox: code review assignment, reviewer comments, PR approval, required status check failures, and more.

Inbox automatically assigns attention based on PR activity. The following reasons may be assigned for getting attention:

* A code review has been assigned to you
* A reviewer commented on a PR authored by you
* A reviewer approved a PR authored by you
* Someone manually assigned the attention to you
* A required status check is failing on a PR authored by you

And likewise there may be PRs associated with you but are waiting on actions from others:

* A PR is waiting for the reviewer's comments
* A PR you reviewed is waiting on the author to take an action
* You manually removed attention from this PR
* The PR is in the merge queue waiting to be merged


---

# 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/inbox/attention-reasons.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.