-
Notifications
You must be signed in to change notification settings - Fork 340
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
Can't establish creds #332
Comments
Hey Tim, you’ll need to upgrade to gist v6.0.0 or greater which uses
Github’s new authentication scheme
Sent via Superhuman iOS ***@***.***>
…On Mon, May 31 2021 at 11:15, Tim Booher ***@***.***> wrote:
From a fresh install.
gist-paste --login
Obtaining OAuth2 access_token from github.
GitHub username: my_username
GitHub password:
Traceback (most recent call last):
10: from /usr/bin/gist-paste:140:in `<main>'
9: from /usr/lib/ruby/2.7.0/optparse.rb:1691:in `parse!'
8: from /usr/lib/ruby/2.7.0/optparse.rb:1666:in `permute!'
7: from /usr/lib/ruby/2.7.0/optparse.rb:1569:in `order!'
6: from /usr/lib/ruby/2.7.0/optparse.rb:1575:in `parse_in_order'
5: from /usr/lib/ruby/2.7.0/optparse.rb:1575:in `catch'
4: from /usr/lib/ruby/2.7.0/optparse.rb:1589:in `block in parse_in_order'
3: from /usr/bin/gist-paste:57:in `block (2 levels) in <main>'
2: from /usr/lib/ruby/vendor_ruby/gist.rb:350:in `login!'
1: from /usr/lib/ruby/vendor_ruby/gist.rb:350:in `loop'
/usr/lib/ruby/vendor_ruby/gist.rb:390:in `block in login!': Got Net::HTTPNotFound from gist: {"message":"Not Found","documentation_url":"https://docs.github.com/rest"} (RuntimeError)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#332>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAXAQAWULXICISBOYSLNIDTQNOTTANCNFSM452TGZPQ>
.
|
What if you have enterprise github? Changing the url via |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From a fresh install of gist v5.0.0 on Ubuntu 20.04.2 LTS
The text was updated successfully, but these errors were encountered: