> 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 all open pull requests and where they are going in a team context.

With GitHub, it is surprisingly difficult to see all open pull requests and where they are going in a team context. Especially when you are working in an environment with multiple repositories and lots of cross-team collaboration, it can be easy for pull requests to fall through the cracks. [The Pull Request view](https://app.swarmia.com/pull-requests/our-team) in Swarmia works in real-time and helps teams manage their pull requests in progress, make sure they are moving forward swiftly, and ensure no pull request is forgotten.

Our team heavily uses the pull request view to see if there are PRs that could be merged or if there are PRs waiting for review to help a teammate before starting something new.

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2Fos09c9fWXS5iDA3uyAwn%2FPR%20Inbox.png?alt=media&amp;token=f44edd6b-a524-4205-9c19-52df72411916" alt=""><figcaption></figcaption></figure>

## Pull request flow of delivery graphs

You can see two graphs on top of the Pull Request view giving you a rough idea of how the pull request flow of delivery functions within your team.

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2FNNdwoalFVVv53r7G089W%2FPR%20Inbox%20Overview.png?alt=media&amp;token=b3dd3e81-344a-4f9b-8694-f1437ffb1eb2" alt=""><figcaption></figcaption></figure>

The cycle time graph shows you how long, on average, it takes for pull requests to take from the first commit to be merged. You will also see the split between how long pull requests on average spent in progress versus in review versus merge phase based on the activity in GitHub. Pull Requests move into the "review" state when a review is requested in GitHub and again to the "merge" state when approved. The "waiting for review" status covers the entire review phase. It stays the same whether no one has started yet or a reviewer is actively commenting — until the PR is approved.

The throughput chart shows how many pull requests you get through as a team over time. The colors on the stacked bars represent the status of the pull requests opened on that specific day. In the throughput chart, we focus most on the yellow part. Seeing a lot of yellow in the past would indicate that on some days, we open a lot of PRs but are just unable to get them in. Then it might make sense to focus on getting the old pull requests merged or closed before taking on more work.

## Pull request view filters

Multiple filters on the left side of the page help you separate the signal from the noise.

**Our team** - This is the default filter and it shows you all of the pull requests that have been authored by the members of the team. Not only can you see your own pull requests here, but you can also identify a way to help your teammate by reviewing their pull request waiting for review.

**Participating** - This is a personal filter that is unique to every Swarmia user based on which pull requests you are participating in yourself by authoring it, being assigned as a reviewer, or just participating in the discussion.

**From others** - This filter shows you all of the pull requests sent to your team for review from any other team. This is a neat way to ensure you are also swiftly reviewing pull requests related to team interfaces since these pull requests easily fall through the cracks.

**Bots** - We also separate pull requests authored by bots under their own filter. So if you are using dependency bots or renovates it will not get as noisy when they open a whole lot of dependency prs some night.

**>30 days old** - Under the old PRs we show you everything that is getting so old that you might want to clean them up by closing in GitHub to maintain good GitHub hygiene.

**>24h stale** - The stale PRs are at risk of being forgotten, so it makes sense to check these together with your colleague to see if they are still relevant, and if they are, work through them so no one has to do any major rebasing or anything like that.

**Unlinked** - This filter is one way that Swarmia helps your team link pull requests to issues. Under this filter, you will see all unlinked pull requests and can link them directly through the UI into categories or issues.

**Custom filters** - Below the "Unlinked" filter are a number of custom filters which are up to you to configure as you wish. These filters are called "Investment Categories" in Swarmia, and you can manage them from [the investment category settings](https://app.swarmia.com/settings/investment-categories). These investment categories are also used in different parts of the app; more about them [in this article.](https://help.swarmia.com/configuring-investment-categories)

**Excluded** - If you exclude a pull request in Swarmia you will still be able to access it through this filter on the Pull Request view. If you change your mind about excluding a pull request, you can also re-enable it in the metrics and alerts in Swarmia through here.

## Custom views

Create views for pull requests that do not fit the defaults. For example, platform, infrastructure, and security teams can track repositories they own. Tech leads can follow PRs with labels such as `hotfix` or `needs-design-review`. Engineering managers can compare the review flow of AI-assisted PRs with other PRs. Teams can also follow a high-risk repository during a migration or share a “Release blockers” view. Each custom view includes the same charts and lists as the default views.

### Create a custom view

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2F1ALflOR4t7INf8noizRH%2Fimage.png?alt=media&amp;token=fc6a09d1-283e-4c07-aea4-8d4584c49be5" alt=""><figcaption></figcaption></figure>

1. In the PR inbox sidebar, select **+ Custom view**.
2. Give the view a name and an icon.
3. Add filters for the pull requests you want to see.
4. To scope the view to the selected team, select **Use team selector**. Leave it unselected to see matching PRs across your organization.
5. Save the view.

The view appears in the sidebar with a live count of open PRs. Edit the view to change its name, icon, or filters. You can also delete it there.

### Create a view with Swarmia AI

Describe the view you want to Swarmia AI. For example, ask: “Create a PR inbox view for open PRs in the payments repository.”

Swarmia AI proposes a name, icon, and filters. It previews matching PRs, then saves the view after you confirm. You can also ask it to update an existing view.

### Share a view

Custom views are personal. Only you see them in your sidebar.

To share a view, select **Copy link** and send it to a teammate. They can open it in read-only mode. They can then select **Save for me** to create their own copy.

## Pull request popup

We want to enable you to drill down into the details in Swarmia. By clicking on the three dots on the very right side of any pull request, you can open the pull request popup. This view gives you more details on the individual pull request level.

If you feel like particular pull requests should rather be excluded from the metrics and alerts in Swarmia, you can switch the toggle for any pull request to exclude it from the metrics.

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2FIwkipNPbrdyFI9c8Okgg%2FPR%20Inbox%20Excluding%20from%20metrics.png?alt=media&amp;token=bce0412a-b72e-49d1-8b76-d4331758822b" alt=""><figcaption></figcaption></figure>

## To conclude

[The Pull Request page](https://app.swarmia.com/pull-requests/our-team) 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.