`POST /api/workspace/repo_sync/resolve` — accept the REMOTE version of one conflicted file (#397): force-applies it, overriding last-write-wins. Gated by `sync_mode` (rejected in `ui-only`).
POST
/api/workspace/repo_sync/resolve
const url = 'https://example.com/api/workspace/repo_sync/resolve';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"path":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/api/workspace/repo_sync/resolve \ --header 'Content-Type: application/json' \ --data '{ "path": "example" }'Request Bodyrequired
Section titled “Request Bodyrequired”Media typeapplication/json
Body of POST /api/workspace/repo_sync/resolve.
object
path
required
The conflict path from the pull preview, e.g. resources/prod-smtp.yaml.
string
Examplegenerated
{ "path": "example"}Responses
Section titled “Responses”Media typeapplication/json
One row per entity affected by a pull.
object
action
required
string
reason
Set for skipped / failed rows; absent for the happy path.
string | null
target_id
string | null format: uuid
target_kind
required
Closed catalogue of sync targets a log row can reference.
string
target_slug
required
string
Example
{ "target_kind": "workflow"}