Skip to main content
Every PR your agents open lands in ADE’s PRs tab — the diff, CI checks, comments, and a merge button, without a GitHub browser tab. ADE keeps remote GitHub state warm through background polling while treating your local git state as the source of truth for merge and conflict simulation.

​
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.
Create a new pull request from a lane
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.
Files changed and CI checks for a pull request
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. A dismissible AI summary card sits above the timeline — risk areas, reviewer hotspots, unresolved concerns — and regenerates when new commits land.
The PR review and comments view
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 sidebar
The commits section of a PR
The GitHub tab lists every PR in the repository — including ones opened outside ADE — with label filters, CI badges, review indicators, and the linked lane’s color, so a glance correlates a PR with the lane that produced it.

​
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

A PR opened from a child lane targets its parent lane’s branch, not main — so a chain of dependent PRs each gets reviewed on its own but merges in dependency order. When a parent PR merges, ADE retargets and rebases the child onto the new base automatically.

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.

Upstream rebase chain

When a child is behind its parent — which may itself be behind its parent — the Rebase view shows the full chain so you can fix several descendants by rebasing one ancestor.
See Stack lanes for the lane side of stacking.

​
Merge queue

For landing several PRs in sequence, a merge queue runs each one through an explicit state machine with visibility into every step.
The queue picks the next pending entry, optionally rebases it if it’s behind, waits for CI when CI gating is on, then merges it with your chosen method. Each entry moves through pending → rebasing → landing → landed (or pauses for attention), and the tab shows where it’s stuck and why.
With auto-resolve on, a merge conflict during landing launches a Codex or Claude CLI resolver in the lane’s worktree. ADE commits and pushes the resolution, then retries the land — so a conflict mid-queue doesn’t stall the whole stack.
A paused queue waits for you; resume it when ready. Cancelling force-fails any in-flight entry cleanly rather than leaving it half-landed, and you can reorder entries before they land.

​
Conflict simulation

Before you hit Merge, ADE predicts whether the PR lands cleanly on its base by running git merge-tree locally — no actual merge required. A predicted conflict disables the merge button (unless you opt into bypass) and surfaces the conflicting files. The same engine powers integration (merge-plan) proposals and the Rebase view.
PR sources and rebase options
ADE uses your GitHub authentication. If PR data is missing, check GitHub access in Settings.

Review

Run an on-demand AI review on a PR — or any diff — before you merge.

Conflicts

Detection, simulation, and AI-assisted resolution across lanes and PRs.