fabro/docs/api-reference
Bryan Helmkamp 0bf2dd30ef
refactor(server): collapse 409 conflict into standard ApiError
Replace hand-built 409 response that inlined {errors,pull_request} with
a regular ApiError::with_code(CONFLICT, ..., "pull_request_exists") and
drop the optional pull_request field that had been added to the
ErrorResponse OpenAPI schema solely to carry the existing record.

Clients receiving a 409 can GET /runs/{id}/pull_request to retrieve the
stored record when they need it — the detail string still includes the
existing html_url, which is the field most clients branch on.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-23 22:45:29 -04:00
..
client-sdks.mdx Rename fabro-api-types to fabro-api with progenitor client generation 2026-04-03 11:17:27 -07:00
demo-mode.mdx refactor(server): remove inbound TLS termination 2026-04-19 10:43:57 -04:00
fabro-api.yaml refactor(server): collapse 409 conflict into standard ApiError 2026-04-23 22:45:29 -04:00
overview.mdx refactor(server): remove inbound TLS termination 2026-04-19 10:43:57 -04:00