neosourceDocs
Search docs

Un-quarantine a test

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

removeQuarantine

Removes `test_id` from the repo's quarantine list — the test goes back to blocking merge on failure. Requires write access on the repository.

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

fetch

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

Path parameters

ownerrequired

string

reporequired

string

test_idrequired

The stable `test_id` key (`classname::name`, or bare `name` when the report carried no classname — see `TestCaseFailure::new`).

string

Responses

204Test un-quarantined

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