Closed saschanaz closed 4 years ago
Okay, this is because the token didn't have the repo
access. Could you add a warning to the readme so that newbies like me won't panic?
Thanks for opening the the issue. Adding info on the required repo
access is a good idea. But I think we could also throw a more helpful error.
The GitHub API often returns a 404
if the authentication is not sufficient to access something.
Update: I've updated the README
This might be a noob question, but I keep getting HTTP 404 when calling
createPullRequest
. Looking at the error stack, it seems it fails to create a fork, but what would it even mean when creating a fork?Manually creating a fork bypasses that error and then creates a new 404 error when trying to create a tree.
I'm using:
and giving personal access token for authentication.