> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/features/managing-pull-requests-in-progress-with-the-pull-request-view.md).

# PR inbox

See every open pull request your team owns, sorted by what it needs next, and move through them quickly with a reading pane and keyboard shortcuts.

The [PR inbox](https://app.swarmia.com/pull-requests/our-team) shows your team's open pull requests in real time, sorted by what they need next. It helps you keep track of PRs across repositories and cross-team reviews, find those ready to merge or waiting for review, and help a teammate before starting new work.

## How the inbox is laid out

The inbox has four parts:

1. **Sidebar**: built-in views and your custom views, each with a count of open pull requests. Collapse the sidebar to give the list more room.
2. **Status tabs**: split the open pull requests in the selected view by status. Tabs with no pull requests are hidden.
3. **Main list**: Filtered list of PRs, grouped by their status, or other property.
4. **PR details**: Select a PR to see its details, next to the list.

![PR inbox overview](https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2FuEk9jvRzuJxcZNcymubg%2Foverview-final.webp?alt=media)

## 1A. Sidebar: Built-in views

* **Our team**: The default view. Pull requests owned by the selected team, including your own pull requests and teammates' pull requests waiting for review.
* **Participating**: Your personal view. Pull requests you authored, are asked to review, or take part in.
* **From others**: Pull requests from other teams that ask your team for a review, so reviews on shared code don't get missed.
* **Bots**: Pull requests created by bots, such as Dependabot or Renovate, kept separate so they don't add noise.
* **Old**: Pull requests older than your team's maximum pull request age working agreement. Close the ones that are no longer needed.
* **Stale**: Pull requests with no activity in the last 24 hours. Check with the author whether they are still needed, and finish them before they need a big rebase.
* **Unlinked**: Pull requests with no linked issue or investment category. Link them from the inbox.
* **Investment categories**: One view per [investment category](https://help.swarmia.com/configuring-investment-categories). Set them up in [investment category settings](https://app.swarmia.com/settings/investment-categories).
* **Excluded**: Pull requests excluded from metrics and alerts. Include them again from here.

## 1B. Sidebar: Custom views

Create a custom view to follow PRs by repository or label, compare AI-assisted PRs, or track release blockers. Custom views have the same status tabs, reading pane and view options as built-in views.

* Select **+ Custom view** in the sidebar, then choose a name, icon and filters.
* Select **Use team selector** to show only the selected team's PRs, or leave it unselected to see matching PRs across your organization.
* Save the view. Open it from the sidebar to edit its name, icon or filters, or delete it.

You can also describe a view to **Swarmia AI**. It suggests a name, icon and filters, previews matching PRs, and saves the view after you confirm. You can also ask it to change an existing view.

Custom views are personal. To share one, select **Copy link** next to its title. Teammates can open it read-only and select **Save for me** to create their own copy.

## 2. Status tabs

Each open pull request has one status, based on its GitHub or GitLab activity:

![Pull request status tabs](https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2F4vLS7HVd3VlkCHvqpffd%2Fstatus-final.png?alt=media)

* **Draft**: Not ready for review.
* **In progress**: Being worked on before review.
* **Waiting for review**: Review requested, and nobody has reviewed it yet.
* **In review**: Reviewed, but not approved yet.
* **Changes requested**: A reviewer asked for changes.
* **Ready to merge**: Approved and waiting to be merged. Checks and merge conflicts aren't taken into account.

The **Merged** and **Closed** tabs show finished pull requests, so you can see what the team got done.

## 3. Pull request rows

Each row shows the pull request's title, repository and number, author, and status. Depending on how wide the list is, rows can show:

* **Size**: lines changed.
* **CI**: the status of checks.
* **Comments**: the number of comments.
* **Reviewers**: who is asked to review and how they responded.
* **Age**: how long the pull request has been open, not counting weekends.
* **Last activity**: when something last happened on the pull request.

A dot next to a pull request means it has new comments since you last opened it. The inbox remembers what you've read on each device.

To open a pull request in GitHub or GitLab, use **Open in GitHub/GitLab** in the row menu, or click its PR key.

### Stacked pull requests

When pull requests are stacked on top of each other, the inbox groups them under the first pull request in the stack, in stack order. A stack badge shows each pull request's position in the stack.

* Click the badge to expand or collapse the rest of the stack.
* Hover over the badge to see every pull request in the stack, including merged and closed ones, and the branch the stack merges into.
* Open any pull request in the stack in the reading pane.

![Stacked pull requests in the inbox](https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2FF7Z9X7zFwtUjEYsc6QkL%2Fstacks.webp?alt=media)

## 4. PR details

The PR details pane shows the selected pull request without leaving the inbox:

* Last activity and approvals
* **Reviewers** and their responses
* **Checks**
* **Activity**: the latest comments and reviews

From the details panel, you can go to the next or previous pull request, copy a link, open the pull request in GitHub, or review it in Swarmia. Drag the edge of the panel to resize it.

![PR details pane](https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2Fx6kkypSweJsq0qIiuJ5Y%2Fdetails-final.webp?alt=media)

## View options

Open **View options** to change how the list looks. Your choices are saved for you.

* **Group by**: status, author, repository, investment category, linked issue, or no grouping. Collapse any group.
* **Density**: **Default** or **Compact** rows.
* **Columns**: show or hide size, CI, comments, reviewers, age and last activity.
* **Bot PRs** and **Draft PRs**: hide pull requests created by bots, or draft pull requests.

![PR inbox view options](https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2FBTf7PVg8v8eImF4uEurm%2Foptions.webp?alt=media)

## Act on pull requests

* **Select several pull requests** to act on them together.
* **Link** a pull request to an issue or investment category from its row.
* **Exclude from metrics** to leave a pull request out of Swarmia's metrics and alerts. Find it again in the **Excluded** view.

We’re working on introducing more actions in the inbox view soon to make it easier for you to make quick changes and review them faster.

## To conclude

The Pull Request page in Swarmia helps team members stay on top of their pull requests and make sure they are moving forward without any pull request falling through the cracks. If you want to make managing pull requests in progress even easier, we recommend looking into the [Swarmia personal Slack and Microsoft Teams notifications for pull requests](https://help.swarmia.com/personal-notifications).


---

# 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://help.swarmia.com/features/managing-pull-requests-in-progress-with-the-pull-request-view.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.
