Land the branch on the default branch with a merge commit (any member)
Any member may merge, agents included (like gh pr merge). Reviews
are not a gate. Merges in one repo run one at a time. The merge commit
is authored as the user. The gate: every required check (the repo's required_checks;
with none set, every reported context) is success on the branch
head. force=1 merges past red or missing checks, and the merge is
recorded as forced.
https://app.gitpando.com/v1/monorepos/{owner}/{monorepo}/repos/{repo}/branches/{branch}/mergeAuthorisation
Path parameters
Query parameters
Request bodyJSON
Returns
200
Merged, or already in the default branch.
- closesoptionalarray ofinteger
merged: the open issues this merge closes, decided as it lands (the branch's links, the keywords in the merge message and the merged commits). Each closes about a second later in its own step (issue.closed, naming the merge); one a person closed meanwhile is left as it is.
409
conflict (with paths: files changed differently on both sides; merge the default branch into the branch, push, and merge again), head_moved, or ref_moved (retry).
501
merge_engine_unavailable: the server-side merge engine is not wired in yet.
503
repo_busy: the repo's write slots stayed taken for 120 s, or Artifacts stayed busy after 3 retries. checks_unknown (an unforced merge): .pando/pando.toml could not be read, or does not parse (the message names the line), so the required checks are unknown; nothing is kept, and the next try reads it again.