Cancel a prepared GitHub ref transaction
DELETE/api/repos/{owner}/{repo}/github-ref-transactions/{id}
cancelGithubRefTransaction
Cancels a `github_managed` repository's `prepared` write-through transaction — one that was recorded but never sent to GitHub — and releases its staged objects. Requires repo admin. Idempotent: an already-cancelled transaction answers `200` as it is. An `ambiguous` transaction answers `409 conflict` (resolve it with provider proof instead); any other state answers `409 conflict`.
Requires authentication using a bearer token or a session cookie — see tokens and scopes.
curl
curl -X DELETE 'https://neosource.dev/api/repos/OWNER/REPO/github-ref-transactions/ID' \
-H 'Authorization: Bearer $NEOSOURCE_TOKEN'fetch
fetch("https://neosource.dev/api/repos/OWNER/REPO/github-ref-transactions/ID", {
method: "DELETE",
headers: {
Authorization: "Bearer $NEOSOURCE_TOKEN",
},
});Path parameters
ownerrequiredRepository owner or organization slug.
reporequiredRepository name.
idrequiredThe ref transaction id (a UUID), as a paused push or a band-2 notice names it.
Responses
200Cancelled
application/json
Standard errors
Bodies documented once for the whole API — see standard errors.
- 400Bad Request — one of: invalid_input
- 401Authentication required
- 403Forbidden — one of: forbidden
- 404Not Found — one of: not_found
- 409Conflict — one of: conflict, github_ref_proof_mismatch
- 423Locked — one of: busy
- 429Rate limited — retry after the `Retry-After` header
- 500Internal server error
- 502Bad Gateway — one of: upstream
- 503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
- 504Gateway timeout — the request exceeded the server's handling budget