> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/dashboard/runs/pull-requests.md).

# Pull Requests

Browse a project's runs grouped by the pull request that triggered them

The **Pull Requests** page lists the pull requests that CI reported runs for within the selected date range (the last 30 days by default), one row per pull request, with the status of its latest run and a strip of its recent runs. It answers "which open pull requests are failing, and since when?" without scanning the flat run feed.

To open it, select a project and click **Pull Requests** in the sidebar.

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2Fgit-blob-0e8dcc0f8dba07b4e9abbb65b2ee2f1f16f95fff%2Fpull-requests-list.png?alt=media" alt="The Pull Requests page listing six pull requests with their author, latest run status, recent runs and run count"><figcaption><p>Pull requests of a project, most recently run first</p></figcaption></figure>

{% hint style="info" %}
A run appears on this page only when CI reports it with pull request information, for example a GitHub Actions `pull_request` workflow or a GitLab merge request pipeline. Runs from branch pushes stay on the Runs page only. A row's title is the pull request title that CI reports, or the latest run's commit message when CI sends no title. It does not follow the project's Run Title Source setting. Authors and commit messages come from the run's git data; see [Commit Information](/dashboard/runs/commit-information.md).
{% endhint %}

## Columns

| Column       | Description                                                                                                                        |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
| Pull request | Number and title. When the page mixes repositories, rows outside the most common one show their repository name before the number. |
| Author       | Commit author of the latest run                                                                                                    |
| Latest run   | Status of the most recent run                                                                                                      |
| Recent runs  | One dot per recent run, oldest to newest, colored by status                                                                        |
| Runs         | Total number of runs for the pull request                                                                                          |
| Last run     | When the most recent run was created                                                                                               |

The **Columns** menu turns the optional columns on and off: **Author**, **Branch**, **Tags**, **Environment** and **First run**. Author is on by default. Environment turns on by itself when a row on the page reports an environment. First run is shown only when the list is sorted by first run.

## Expanding a Pull Request

Clicking anywhere on a row, or pressing <kbd>Enter</kbd> on a focused row, expands it into a timeline of the pull request's recent runs, newest first. Each run shows its commit message, the commit author and short SHA, the number of failed tests, its duration and when it was created.

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2Fgit-blob-f41634209eb64f72da420570a2043011b7c982d4%2Fpull-requests-expanded-row.png?alt=media" alt="An expanded pull request showing two runs of the same commit; the older failed run is muted and marked as rerun"><figcaption><p>The earlier run of commit 1c0830d8 is muted because the same commit ran again after it</p></figcaption></figure>

When the same commit runs more than once, for example after a retry in CI, the earlier runs are muted and marked **This commit ran again after this run**, so the result that stands is the latest one.

When a pull request has more runs than the timeline shows, a **View all N runs** link opens the Runs page filtered to that pull request, keeping the current search and date range.

## Previewing a Run

Clicking a run in the expanded row, or a dot in the **Recent runs** column, opens the run in a drawer over the list. The drawer has the full run page, including its tabs, filters and test details, and the list keeps its scroll position, filters and expanded rows underneath.

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2Fgit-blob-55c8c3850a269a6030e735dc8afa3d4abe009bb6%2Fpull-requests-preview-flow.gif?alt=media" alt="Expanding a pull request and opening one of its runs in the preview drawer"><figcaption><p>Expanding a pull request and previewing one of its runs</p></figcaption></figure>

* **Open run** in the drawer header opens the full run page.
* Opening a test inside the drawer shows it over the run, with **Back to run** to return.
* <kbd>Esc</kbd> closes an open test first, then the drawer.
* <kbd>Ctrl</kbd>/<kbd>Cmd</kbd>-click on a run opens the run page in a new tab instead of the drawer.

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2Fgit-blob-95f77070a563a8adeb1b089769441b24302fd317%2Fpull-requests-run-preview.png?alt=media" alt="The run preview drawer showing a passed run of pull request 482 with its summary and test list"><figcaption><p>A run of pull request #482 in the preview drawer</p></figcaption></figure>

## Searching and Filtering

* **Date range** - pull requests with runs in the selected range. The default is the last 30 days. When the range is empty, **Use last 90 days** widens it.
* **Search** - matches a pull request's title, number (`#482` or `482`) or branch.
* **Status chips** - **Failed**, **Failing**, **Running** and **Passed** filter by the status of each pull request's latest run. More than one chip can be selected.
* **Filter** - narrows the list by **Branch**, **Author**, **Tag** or **Environment**. Each active filter appears as a removable pill under the toolbar.

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2Fgit-blob-b2ef658a22d0a43a4fe94df300258367ad9d16b5%2Fpull-requests-filter-menu.png?alt=media" alt="The Filter menu with Branch, Author, Tag and Environment options"><figcaption><p>The Filter menu</p></figcaption></figure>

Status and search are checked against each pull request's latest run. When nothing matches, **Clear filters** resets the search, chips and filters.

## Row Actions

Right-clicking a row opens its actions:

* **Open latest run**
* **Open on** the Git host, for example `github.com`
* **Copy branch name**
* **Filter by this author**
* **Filter by this branch**

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2Fgit-blob-d4b366b6427f001e6f5cbdbbae41b93de12f0a99%2Fpull-requests-row-menu.png?alt=media" alt="The row context menu of pull request 482"><figcaption><p>Actions for a pull request</p></figcaption></figure>

## Display Options

The **Display** menu controls how the list is ordered and laid out.

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2Fgit-blob-17893702536f258a7556e538441f3ec310b4c5fa%2Fpull-requests-display-menu.png?alt=media" alt="The Display menu with Sort by, direction, Rows per page, Density and Group stacked pull requests"><figcaption><p>The Display menu</p></figcaption></figure>

| Option                      | Values                                                                                                   |
| --------------------------- | -------------------------------------------------------------------------------------------------------- |
| Sort by                     | **Last run** (default), **First run** or **Number of runs**                                              |
| Direction                   | **Newest first** / **Oldest first**, or **Most runs first** / **Fewest runs first** when sorting by runs |
| Rows per page               | **20** (default) or **50**                                                                               |
| Density                     | **Compact** (default) or **Comfortable**, which adds the source and destination branches under the title |
| Group stacked pull requests | On by default. See [Stacked Pull Requests](#stacked-pull-requests).                                      |

Density, rows per page, column choices and stacked grouping are saved per project in the browser. A shared link that sets the page size keeps it for everyone who opens it.

## Stacked Pull Requests

A pull request is stacked when its destination branch is the source branch of another pull request in the same repository, for example `feat/validation-helpers` into `feat/checkout-validation`.

With **Group stacked pull requests** on, a stacked pull request is placed directly under the pull request it is stacked on, and a stack icon marks each member of the group. In the screenshot at the top of this page, #486 is stacked on #485. A stacked pull request whose parent is not directly above it, such as a parent on another page, shows a **Stacked on #N** badge instead.

## New Runs

The list refreshes every minute, and more often while a latest run is still in progress. When new runs change the first page while a later page is open, a **New runs · Back to newest** button returns to the top of the list.

## Missing Commit Information

When most pull requests on the page have runs without a commit message or author, a warning explains that CI sends only the commit SHA. Runs affected are marked with a warning icon. The warning offers **Fix with AI**, which hands an AI assistant a prompt for fixing the CI configuration, and a **Setup guide** link to [Commit Information](/dashboard/runs/commit-information.md). Dismissing the warning hides it for that project.


---

# 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.currents.dev/dashboard/runs/pull-requests.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.