The pull request page now renders UI.stack_map/1 — the stack as an ordered rail with layer states, delivered in 40c2922 — but the reader still cannot act on the stack from the page. GitHub's stack map offers add-to-stack and unstack directly, its merge box summarizes stack-wide readiness, and a cascading rebase can be triggered from the UI.
Scope
- Enable the rebase-the-stack action (the stack-restack-action button is disabled today) by submitting a restack operation and reporting its progress.
- Offer add-to-stack from the map for an open pull request whose head could extend the stack, once the append flow has a UI.
- Offer unstack from the map's action slot, once the unstack endpoint exists.
- Link the trunk row to the branch's tree view.
- Summarize stack-wide readiness — which layers pass policy and which block the prefix — beside the map.
Depends on the unstack and dissolve API work and pairs with the asynchronous merge work.
Written by Devin
The pull request page now renders UI.stack_map/1 — the stack as an ordered rail with layer states, delivered in 40c2922 — but the reader still cannot act on the stack from the page. GitHub's stack map offers add-to-stack and unstack directly, its merge box summarizes stack-wide readiness, and a cascading rebase can be triggered from the UI.
Scope
Depends on the unstack and dissolve API work and pairs with the asynchronous merge work.
Written by Devin