You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to github fork. The 1st time I ran this command, I entered a wrong username. And after Entering the token, I received the following error:
/var/lib/gems/2.3.0/gems/json_pure-1.5.5/lib/json/common.rb:148:in `parse': 784: unexpected token at '<h (JSON::ParserError)
<head><title>410 Gone</title></head>
<body bgcolor="white">
<center><h1>410 Gone</h1></center>
<hr><center>nginx</center>
</body>
</html>'
from /var/lib/gems/2.3.0/gems/json_pure-1.5.5/lib/json/common.rb:148:in `parse'
from /var/lib/gems/2.3.0/gems/github-0.7.2/lib/commands/commands.rb:229:in `block in load'
from /var/lib/gems/2.3.0/gems/github-0.7.2/lib/github/command.rb:25:in `call'
from /var/lib/gems/2.3.0/gems/github-0.7.2/lib/github.rb:76:in `invoke'
from /var/lib/gems/2.3.0/gems/github-0.7.2/lib/github.rb:70:in `activate'
from /var/lib/gems/2.3.0/gems/github-0.7.2/bin/gh:8:in `<top (required)>'
from /usr/local/bin/gh:23:in `load'
from /usr/local/bin/gh:23:in `<main>'
Now, every time I run github fork, I get this error. I want github the command to forget about these credentials, How do I do this?
I'm trying to
github fork
. The 1st time I ran this command, I entered a wrong username. And after Entering the token, I received the following error:Now, every time I run
github fork
, I get this error. I wantgithub
the command to forget about these credentials, How do I do this?In addition, The webpage in which I created my token is https://github.com/settings/tokens and not https://github.com/account which rederects you to https://github.com/settings/profile. I'm not sure right now If I created a token as I should have because I entered my username wrong as well. But perhaps the command line guide when running
github fork
for the 1st time should include the URL: https://github.com/settings/tokensThe text was updated successfully, but these errors were encountered: