Revert a repository operation
POST/api/repos/{owner}/{repo}/operations/{operation_id}/revert
revertRepositoryOperation
Writes a new operation that inverts the bookmark moves of `operation_id`. The original op stays in the log; the revert appears as a sibling row with `kind = 'revert'` and `reverts = <operation_id>`.
Requires authentication using a bearer token or a session cookie — see tokens and scopes.
curl
curl -X POST 'https://neosource.dev/api/repos/OWNER/REPO/operations/OPERATION_ID/revert' \
-H 'Authorization: Bearer $NEOSOURCE_TOKEN'fetch
fetch("https://neosource.dev/api/repos/OWNER/REPO/operations/OPERATION_ID/revert", {
method: "POST",
headers: {
Authorization: "Bearer $NEOSOURCE_TOKEN",
},
});Path parameters
ownerrequiredreporequiredoperation_idrequired64-char hex of the 32-byte operation id.
Responses
200Revert recorded
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: already_exists, conflict, non_fast_forward
- 423Locked — one of: busy
- 429Rate limited — retry after the `Retry-After` header
- 500Internal server error
- 503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
- 504Gateway timeout — the request exceeded the server's handling budget