Skip to main content
General·HTTP 422·API, CLI, FE

Branch or commit not found

ref_not_found

The repository has no branch, tag or commit with the name sent, or it has no commits yet.

What this means​

The name is misspelled, the branch was deleted, or the commit was never pushed to this repository.

How to fix it​

Check the branch, tag or commit on your Git provider and send one that exists. Leave it out to use the repository's default branch.

Retry behavior​

Sending the same request again gets the same answer.

How it appears in the response​

ComputeSphere returns errors as RFC 7807 Problem Details. The type field is the docs URL for this page — switch on code in your client.

{
  "type":    "https://docs.computesphere.com/errors/ref_not_found",
  "title":   "Branch or commit not found",
  "status":  422,
  "code":    "ref_not_found",
  "detail":  "The repository has no branch, tag or commit with the name sent, or it has no commits yet.",
  "instance": "/v2/…",
  "request_id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "trace_id":   null
}

The Content-Type header is application/problem+json. On field-level validation errors a non-empty errors[] array also appears, each entry carrying its own docs_url for the offending field.