Skip to main content
The Graph view turns your repository state into a map. Use it when the lane list is not enough and you need to see how work relates.

Topology

See lanes, branches, PR links, and stack relationships.

Merge risk

Spot branches that are likely to conflict before merge time.

Navigation

Jump from the graph into a lane or PR.

​
What appears on the graph

NodeMeaning
LaneA registered ADE lane and its branch.
PRA GitHub pull request linked to a lane.
BranchA branch ADE can see but has not registered as a lane.
Edges show base-branch and stack relationships.

​
When to use it

  • Before merging several active lanes.
  • When a stack gets hard to reason about.
  • When you need to know which work depends on another branch.
  • When an agent has created several lanes and you want the map.

​
Merge simulation

ADE can simulate merges and surface likely conflicts. Treat the result as a warning system, not a substitute for final CI and review. Re-run simulation after major commits.
Graph is most useful late in a work session, when you are deciding merge order and cleanup.