Skip to content
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

hub clone org/repo.wiki fails with "Repository not found" #1172

Closed
glittershark opened this issue May 4, 2016 · 6 comments
Closed

hub clone org/repo.wiki fails with "Repository not found" #1172

glittershark opened this issue May 4, 2016 · 6 comments

Comments

@glittershark
Copy link

No description provided.

@mislav
Copy link
Owner

mislav commented Aug 7, 2016

Sorry for the late reply:

  1. Does the org/repo repository exists?
  2. Does it have wiki enabled?
  3. You can enable debugging with HUB_VERBOSE=1 hub clone org/repo.wiki. Please do that and see if anything jumps at you. You can paste us the debug log, with parts of it anonymized if you wish.

@glittershark
Copy link
Author

glittershark commented Aug 7, 2016

❯ HUB_VERBOSE=1 git clone [org redacted]/[repo redacted].wiki
$ git config alias.clone
$ git config hub.protocol
$ git config --bool hub.http-clone
> GET https://api.github.com/repos/[org redacted]/[repo redacted].wiki
> Authorization: token [REDACTED]
< HTTP 404
{"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
$ git config hub.protocol
$ git config hub.protocol
$ git clone git://github.com/[org redacted]/[repo redacted].wiki.git
Cloning into '[repo redacted].wiki'...
fatal: remote error:
  Repository not found.

some more information:

  • repo definitely exists
  • repo wiki definitely exists
  • repo is private
  • it looks like since the github API request is returning a 404 it's trying to clone using git://, which obviously fails since it's a private repo

@glittershark
Copy link
Author

Did some snooping - looks like 93eccff, which master has but 2.2-stable doesn't, fixes the issue. Will leave closing this now vs at the next version release up to you

@mislav
Copy link
Owner

mislav commented Aug 8, 2016

Thanks for all the info! You're right that that commit fixes it, and I'll port this to 2.2-stable to be in the next 2.2.4 release. Stay tuned!

@mislav mislav added this to the v2.2.4 bugfix release milestone Aug 8, 2016
@glittershark
Copy link
Author

thanks @mislav!

@mislav
Copy link
Owner

mislav commented Aug 11, 2016

Fix now included in the 2.2.4 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants