Thanks for the patch. I believe you need repo scope since repo:keys does not exist. I'd love to fully document the scopes required for each method, but I think we're better off automating that via the build process to to pull from the X-Accepted-OAuth-Scopes header or something. I'm going to close this until we can do it across the board.

Indeed that would be a lot better if it was generated.

Interestingly when I tried to add a key with a repo scope it wouldn't work but with repo:keys it did. need to try it again with just the repo scope.

Cheers

Stay Frosty
Colin
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

On Sunday, 21 October 2012 at 14:26, Wynn Netherland wrote:

Thanks for the patch. I believe you need repo scope since repo:keys does not exist. I'd love to fully document the scopes required for each method, but I think we're better off automating that via the build process to to pull from the X-Accepted-OAuth-Scopes header (http://developer.github.com/v3/oauth/#scopes) or something. I'm going to close this until we can do it across the board.

—
Reply to this email directly or view it on GitHub (#163 (comment)).