PR stacks

See how a conversation’s pull request relates to other PRs, beside the chat. The view reads GitHub metadata and links each PR to GitHub.

Open the stack

Choose View PR stack... from the PR button’s menu or the Code menu. View > PR stack and PR stack in the side pane’s + open the same tab. It needs a conversation with a working folder and GitHub access through the GitHub CLI.

The current PR is highlighted. Each row shows its title, number, head and base branches, and whether it is open, a draft, merged or closed. Click a PR to open it on GitHub. Refresh asks for current metadata; changes to the conversation’s PR and completed turns also refresh a visible stack.

Read the relationships

A confirmed parent appears above its dependents. Siblings share a parent; their order does not mean one depends on another. A standalone PR shows its base branch.

Confirmation uses GitHub’s repository, branch and commit metadata. A matching branch name alone is not enough. When several parents are possible, they stay separate links with an explanation. Missing metadata, a partial response, a lookup limit or a failed connection is shown explicitly.

A merged PR that GitHub has retargeted to the default branch may no longer reveal its historical parent. Dependents in a different fork repository are not searched. The view is bounded to 24 related PRs, so it can say the result is incomplete for a large stack.

Opening or refreshing the stack does not rebase, restack, push, publish or merge anything.

Keep the tab available

Click the pin beside the tab’s name, or choose Pin tab in its right-click menu. The pin belongs to this conversation and survives reopening the window or restarting buddylist. Unpin tab returns it to its usual behavior; Close removes it and its pin.

An archived conversation can still read its stack. If its checkout is missing, a pinned tab explains why it is unavailable and can still be closed or unpinned. See the conversation guide for the other tabs and pin controls.