Patch an existing change by updating metadata and/or applying file operations, then snapshot the result into a new change-owned commit. File content must be base64-encoded. When the change is conflicted, files writes are refused; submit a resolutions array instead to incrementally resolve conflicts — when every contested path is resolved the change becomes clean. files and resolutions are mutually exclusive on a single PATCH. A PATCH on a conflicted change without resolutions returns 409 MERGE_CONFLICT with a details.conflict_paths array listing the still-conflicted paths.
Documentation Index
Fetch the complete documentation index at: https://docs.mesa.dev/llms.txt
Use this file to discover all available pages before exploring further.
writeBearer authentication header of the form Bearer <token>, where <token> is your auth token.
Organization slug
1Repository name
1^[zyxwvutsrqponmlk]{32}$11^[0-9a-f]{40}$Conflict resolutions to apply to a conflicted change. When present, the change advances to a new commit: fully resolved paths collapse into the target-term tree and the change becomes clean when no conflicts remain. files and resolutions are mutually exclusive — a conflicted change must be resolved via resolutions before regular file writes land.
A single caller-supplied resolution. Whole-file variants carry content OR take (not both); per-hunk variants carry hunks. Whole-file replaces the merged content at path. Per-hunk requires all hunks for the path to be resolved.
Change updated
^[zyxwvutsrqponmlk]{32}$^[0-9a-f]{40}$True when the change current commit still contains unresolved conflicts