ReferenceAPI overview
Git errors
Four error codes tell that GitHub, GitLab or a git remote refused a request or gave no answer.
GitLab needs an OAuth application first: 400 git_application_required.
1 / 4
These codes come from the provider, not from the authentication of Ferry. See Connect GitHub or GitLab.
The codes
| Status | code | When |
|---|---|---|
| 400 | git_application_required | GitLab needs an OAuth application for this server before an account can authorize it. |
| 400, 409 | git_authorization_rejected | GitHub or GitLab refused an authorization. |
| 502 | git_provider_unavailable | The server cannot reach GitHub or GitLab, or the provider answered with an error. |
| 502 | git_remote_unreachable | The remote of a repository refused, was not there, or gave no answer in time. |
Send the client_id and the client_secret of the application with POST /api/v1/git/authorize.
400: for the authorization that you make now. Examples: the provider refused a token or a code, or the user said no.409: for the authorization that a git connection has in the store. This authorization is no longer valid: expired, revoked, uninstalled or not complete.- Never
401. This status is for the authentication of Ferry itself.
git_provider_unavailable: while you authorize an account, or while Ferry lists the repositories of a git connection.git_remote_unreachable: while Ferry lists the branches of a repository (GET /api/v1/git/branches). The message tells why. It also tells what to do when the repository looks private.