The PRs tab: every pull request in the repo with its CI and review state.
PR management walkthrough on YouTube.
Open a PR from a lane
Because every lane is its own branch, opening a PR is one step. Pick the lane, confirm the base branch, and ADE creates the PR — from the lane, from a chat, or straight from the PRs tab. The draft title and body are prefilled from the lane’s commits and diff, and ADE returns both the GitHub URL and an ADE deep link so an agent can drop both into its closeout note.Branch names are validated before submission, so an invalid git ref fails in ADE with a clear message instead of an opaque GitHub API error.
Inspect the PR
The detail view splits a PR into focused tabs — Overview, Files, CI / Checks, and Activity — and each one loads on its own, so a slow comments fetch never holds up the checks or files. The Overview renders as a Timeline + Rails layout: a central event timeline (commits, comments, reviews, label changes, merges, deployments), a left rail with the commit list and push-time checks, and a right rail with merge readiness, reviewers, labels, and participants. You can reply to review threads, resolve them, react to comments, request reviewers, and submit your own review — approve, request changes, or comment — without leaving ADE. The PRs tab lists every PR in the repository — including ones opened outside ADE — with filters for label, author, and assignee, CI badges, review indicators, and the linked lane’s color, so a glance correlates a PR with the lane that produced it. Each PR’s size is split into code, tests, and docs, so you can tell a large change from a large test suite.Merge it
When checks pass and reviews are in, merge from the readiness panel. Pick the method — squash, merge, or rebase — and land it.Auto-merge
Let the PR merge itself the moment it’s green — useful for stacked work where each child waits on its parent.
Merge bypass
When branch protection blocks a clean merge, opt in to retry with an admin merge. GitHub still decides whether the bypass is allowed.
Post-merge cleanup
ADE deletes the branch, archives the lane if configured, refreshes the base, and rescans rebase needs — all best-effort, so cleanup never undoes a good merge.
Stacked PRs
For a GitHub stack, each lane has its own PR targeting the branch below it. Useade prs stacks to inspect the stack; rebase a lane when its compare base advances.
Dependency-ordered landing
Land a whole stack in one action: ADE merges the root, then each downstream PR in order, auto-rebasing any descendant that drifted and stopping on the first failure.
Conflict simulation
Before you hit Merge, ADE predicts whether the PR lands cleanly on its base by runninggit merge-tree locally — no actual merge required. A predicted conflict disables the merge button (unless you opt into bypass) and surfaces the conflicting files. When updating a PR branch hits conflicts, ADE puts a resolve prompt in the lane’s chat.
ADE uses your GitHub authentication. If PR data is missing, check GitHub access in Settings.
History
Inspect the commits, chats, and agent work behind a pull request.
Conflicts
Detection, simulation, and AI-assisted resolution across lanes and PRs.