404 error on a repository that exists?Typically, we send a 404 error when your client isn't properly authenticated.
You might expect to see a 403 Forbidden in these cases. However, since we don't
want to provide any information about private repositories, the API returns a
404 error instead.
To troubleshoot, ensure you're authenticating correctly, your OAuth access token has the required scopes, and third-party application restrictions are not blocking access.