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

Error creating fork: Not Found (HTTP 404) #912

Closed
wolph opened this issue May 28, 2015 · 2 comments
Closed

Error creating fork: Not Found (HTTP 404) #912

wolph opened this issue May 28, 2015 · 2 comments

Comments

@wolph
Copy link

wolph commented May 28, 2015

Not exactly sure why this is going wrong but it seems I'm unable to fork through hub. I've already re-authenticated but it seems to make no difference.

My worklog:

# HUB_VERBOSE=true hub fork
> GET https://api.github.com/repos/WoLpH/vundle
> Authorization: token [REDACTED]
< HTTP 404
{"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
> POST https://api.github.com/repos/gmarik/vundle/forks
> Authorization: token [REDACTED]
< HTTP 404
{"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
Error creating fork: Not Found (HTTP 404)
Not Found

Anyone has a clue what might be wrong?

Some additional info:

# git branch -v
* master 272d9fe [ahead 1] added support for specifying specific branch/tag/revision while installing
# git remote -v
origin  https://github.com/gmarik/vundle (fetch)
origin  https://github.com/gmarik/vundle (push)
# git branch -v
* master 272d9fe [ahead 1] added support for specifying specific branch/tag/revision while installing
# git status -v
On branch master
Your branch is ahead of 'origin/master' by 1 commit.
  (use "git push" to publish your local commits)
nothing to commit, working directory clean

Versions:

git version 2.3.5
hub version 2.2.1

On OS X installed through brew

@wolph
Copy link
Author

wolph commented May 28, 2015

Ok, I've found the problem. It appears the original repo has been renamed since.

It would be Good if the tool would give a better error. Something like: are you sure repo ... exists? with a working link

@mislav
Copy link
Owner

mislav commented May 28, 2015

GitHub API is going to get repo rename redirects soon, so we'll try to switch to that. Thanks for reporting! #878

@mislav mislav closed this as completed May 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants