-
Notifications
You must be signed in to change notification settings - Fork 188
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
APIV3 switch #84
Comments
Great sigh Cheers Dr Nic Williams - VP Engineering On Tuesday, April 17, 2012 at 3:02 PM, Andrea Brancaleoni wrote:
|
Yeah, the gem is quite confusing now, because it directs the user to get a token from a page that no longer has a token on it. |
As a starter, I modified the code to send in OAuth header and not token at kohsuke@188b226 Various code is still making V2 API call, so this is just one step toward the V3 API migration. |
Am I assuming correctly that "hub" is taking over here? |
A lot of places still call this "official". Kinda confusing as this project looks dormant... |
Nothing that involves the use of the Authentication Token works anymore for the new users.
https://github.com/blog/1090-github-api-moving-on
Like stated here we need to switch over the v3 API using OAuth methods.
The text was updated successfully, but these errors were encountered: