Using the Merge UI
The web app offers detailed information about pull requests, the state of the merge queue, and more.
Last updated
The web app offers detailed information about pull requests, the state of the merge queue, and more.
Last updated
The web app can be found at .
The queue tab provides an overview of the work done by Merge. Merged, testing, and pending PRs should all appear here. Clicking on a row will show the history of that item: click "view more history" to get a better understanding of the item.
The PR details show information about a PR, including a link to the PR in GitHub, the history of the PR within Trunk Merge Queue, and what must be done before a PR can be admitted to the queue for PRs that have not entered the queue yet.
When a PR has not been admitted to the queue yet, Trunk Merge Queue waits for:
Impacted targets to be uploaded for the PRs current SHA (Parallel mode only)
The PR to be mergeable according to GitHub. If the PR is not mergeable yet, this most likely means that the PR is not meeting all branch protection rules you have set (for example, not all required status checks have passed yet) or has a merge conflict with the target branch
The target branch of the pull request to match the branch that merge queue merges into
In the screenshot above the PR's base branch matches the Merge branch, but the impacted targets are not yet uploaded, but it is not mergable on GitHub yet.
The PR Details panel has a dropdown menu (labeled "...") with actions. From this menu, you can:
Remove a PR from the queue. If the PR is "Not Ready", then it will cancel it, preventing it from going into the queue until it is re-queued. If the PR is currently in the queue, it will be removed from the queue, which will restart all PRs that depended on it
Re-queue a PR if it is currently not in the queue
The "Remove from queue" action will remove the PR from the merge queue. If the PR is "Not Ready", then it will cancel it, preventing it from going into the queue until it is re-queued. If the PR is currently in the queue, it will be removed from the queue, which will restart all PRs that depended on it:
PR Details
A PR details page will display a complete history of a PR - state transitions, associated test runs, a visual of what's currently in the Merge Queue, etc. The same dropdown menu described above (labeled "...") is on this page as well.
A tabulated view of all the items that have failed in the Merge Queue, e.g. due to testing.
Trunk Merge Queue will automatically restart failed PRs when it can under certain conditions (see PR states). Since the restart is usually from a failed PR being removed from the queue, other PRs behind it will also be restarted. If you want to manually restart a PR, you can restart it in place using the Restart tests option of the PR dropdown (labeled "...")
There are a couple of reasons you might want to manually restart a PR. First, if a PR ends up in the PENDING_FAILURE state because of something transient like a CI runner disconnecting or flakey tests, you can restart the PR right away instead of waiting for PRs in front of it to pass or fail.
Another reason to restart a PR is if the proper tests don't get kicked off due to a failure in the CI system. For example, if GitHub has an outage and is not triggering workflows or actions properly.
The view of all current PRs being tested by Trunk Merge Queue and their respective queues. Each node shown is a pull request, and each edge indicates that the pull request is testing with the item above and depends on it. All edges point towards the target branch; as items merge, the affected queues restructure. If running in Single mode, this will be a single line showing the testing and merging process.
You can click on any shown PR to navigate to the details page for that PR.
Download any impacted targets that have been uploaded for the PR (uploading impacted targets is only required for mode, but this option will still show regardless of mode if impacted targets have been uploaded for the PR)
