Skip to main content
A merge review should explain what changes, which branch receives the change, and what evidence supports it. The API provides branch previews and merge operations for this review.
Proposal creation, reviewer approvals, and proposal comments are planned. The dashboard merge-review action is not connected. Use the public preview API and keep the human review record in your own review process.
You need access to the agent and distinct source and target branches. The supported merge direction is a non-main source branch into main.
1

Identify the proposed change

Record the source and main branch IDs, current version IDs, reason for the change, and any triage ticket.
2

Inspect the merge preview

Request Preview merged configuration with target_branch_id. Read the combined configuration and conflict information. The force option changes conflict selection; it is not reviewer approval.
3

Review publication readiness

Refresh the preview if either branch changes. An authorized merge must pass publication validation. Managed-model text-only configurations can be eligible; voice and custom-model configurations are blocked.
Publication and deployment are separate. A merged configuration does not demonstrate successful runtime execution. Keep unresolved conflicts and unexecuted tests visible in the review record.
No. Previewing and merging are separate operations. Review the exact inputs again before a merge.
There is no released proposal approval resource or connected approval workflow for branch merges.