Repository Unavailable
repo-unavailable · 502
GitHub didn't answer the API's read of the repository with something it could use, so the fault is upstream.
All pages
Nothing is wrong with the request. A repository GitHub says doesn't exist answers repository-not-found instead.
Besides the members every error carries, this type adds repoPath.
- GitHub was down, or limiting requests, at that moment.
- GitHub answered with an error other than not found.
- Retry after a delay: this is one of the few errors where retrying unchanged is right.
- Don't conclude the repository is missing.
- If it lasts several minutes, check GitHub's own status before reporting it as a Ghaym fault.
json
{
"type": "repo-unavailable",
"title": "Repository Unavailable",
"detail": "Could not reach GitHub to read this repository. Please try again shortly.",
"repoPath": "acme/storefront",
"requestId": "req-1785231000000-4f7b2c9ae",
"timestamp": "2026-07-28T09:30:00.000Z",
"path": "/v1/git/branches",
"method": "GET",
"instance": "GET /v1/git/branches",
"status": 502,
"docs": "https://ghaym.me/docs/errors/repo-unavailable"
}