Delete a repository

DELETE/api/repos/{owner}/{repo}

deleteRepository

Tombstones the repository: it vanishes from every read immediately. An async server-side reaper then cascade-deletes its data (PRs, issues, comments, jobs, grants, operation log, packs). Forks of this repository are KEPT — they are decoupled, not deleted, and continue to resolve every object. Requires repo admin access. Idempotent: deleting an already-deleted repo returns 404.

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' \
  -H 'Authorization: Bearer $NEOSOURCE_TOKEN'

fetch

fetch("https://neosource.dev/api/repos/OWNER/REPO", {
  method: "DELETE",
  headers: {
    Authorization: "Bearer $NEOSOURCE_TOKEN",
  },
});

Path parameters

ownerrequired: Repository owner or organization slug.
string
reporequired: Repository name.
string

Responses

204Repository tombstoned; reaper will cascade

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