Start with the delivery record
Open Delivery → PRs to inspect proposed changes and their checks. Previews & Deploys shows the available deployment evidence. A merged change and a successfully deployed change are separate states.
What is a merge lane?
A merge lane is an integration branch for a group of related work, such as an epic. It lets related changes be reconciled before they reach the shared integration/release path. It is different from a column on the task board.
Availability and prerequisites
Merge-lane routing and merge-train execution are separately controlled capabilities. The reviewed implementation defaults these controls off; ask your organization administrator which are enabled. Do not assume a visible route or a guide means automatic merging is active.
Review before promotion
- Confirm the intended repository, base branch and lane.
- Review the diff, acceptance evidence and required checks.
- Resolve conflicts and review holds; do not bypass them merely to move the card forward.
- Approve or request changes according to your role and organization policy.
- Verify the integration/release result and deployment health before treating the work as delivered.
When parallel work collides
Check overlapping files and dependencies. A lane reduces coordination work but does not guarantee conflict-free changes. Keep rollback and ownership decisions explicit.