Start a merge — detect conflicts (write)
Branches
Start a merge — detect conflicts (write)
Begin merging the branch into main. This recomputes and records conflicts against main’s current state and reports how many changes will auto-merge. Resolve any returned conflicts, then call merge/complete — see the branching guide.
Constraints:
- When the project requires merge approval, personal tokens need the approve permission and machine (project) tokens are rejected.
POST
Start a merge — detect conflicts (write)
Authorizations
API token: tsu_pat_… (PAT) or tsu_proj_… (project token). The token's granted RBAC permissions determine access; see each operation's x-permission.
Path Parameters
Project id (UUID) or id-embedded path slug.
Translation branch id (UUID).

