-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: repo not found #9
Comments
what do you get, when you do this: git remote -v |
I’m getting the same issue — I suspect it has to do with private repos. |
I figured it out; there is a problem with the API. Public and private repos are treated differently. We can't post login credentials to the list and show commands; this returns a 500 error. This would be needed by private repos. Public repos can be queried without posting login and token, so this works. I'll notify the developers. |
I tried adding auth to all commands and it seems to be working fine with public and private repositories |
When I add auth to the show command, it stops working on public and private repos (= returns a 'too many requests' error). What do you get? |
I'm certainly getting this error with private repositories. I have yet to try davidsch's changes to see if it fixes it. For those who are wondering, the changes are in his fork. You can find the changes in the commit: http://github.com/davidsch/github-cli/commit/1ff4b1889d0a626c61253504094e3e062502bea9 |
Posting auth details with the request are now default. It is not documented yet on develop.github.com. Commands work now for public and private repos. Committed in: http://github.com/jsmits/github-cli/commit/ab3eceaf88c0270c55aed30edc4f35d6d1fd773b |
I have created the .ghrc file and the setup went fine without error messages. But when I run any of the commands i get “error: repo not found”.
The text was updated successfully, but these errors were encountered: