Problem
AO takes a session all the way through the lifecycle — working → in review →
ready to merge — and notifies me when CI is green and the PR is mergeable.
But the final step breaks the flow: the PR card only offers a link to GitHub
("one click to the PR"), so the one remaining human action (the merge itself)
requires leaving the app.
Given AO's philosophy of "human steps in at PR time", the PR card is exactly
where that step should be possible.
Proposed direction
A "Merge" button on the PR card / session inspector when the PR state is
ready-to-merge (checks green, approvals satisfied, no conflicts):
- executes merge via the existing
gh integration (AO already acts "as you")
- respects repo merge settings; ideally a small dropdown for
merge / squash / rebase, or just default to the repo's allowed method
- disabled with a tooltip when branch protection blocks merging
- after merge: card transitions to done, worktree cleanup follows the
existing post-merge flow
Alternatives considered
gh pr merge in the session terminal — works, but defeats the purpose of
the board as mission control
- GitHub auto-merge — good for full automation, but not for the
"review, then consciously press merge" workflow AO is designed around
Before submitting
Problem
AO takes a session all the way through the lifecycle — working → in review →
ready to merge — and notifies me when CI is green and the PR is mergeable.
But the final step breaks the flow: the PR card only offers a link to GitHub
("one click to the PR"), so the one remaining human action (the merge itself)
requires leaving the app.
Given AO's philosophy of "human steps in at PR time", the PR card is exactly
where that step should be possible.
Proposed direction
A "Merge" button on the PR card / session inspector when the PR state is
ready-to-merge (checks green, approvals satisfied, no conflicts):
ghintegration (AO already acts "as you")merge / squash / rebase, or just default to the repo's allowed method
existing post-merge flow
Alternatives considered
gh pr mergein the session terminal — works, but defeats the purpose ofthe board as mission control
"review, then consciously press merge" workflow AO is designed around
Before submitting