This repository was archived by the owner on Nov 1, 2017. It is now read-only.
- Notifications
You must be signed in to change notification settings - Fork1.1k
Add reference to required scope for managing private Gists.#62
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
technoweenie added a commit that referenced this pull requestMar 23, 2012
Add reference to required scope for managing private Gists.
izuzak added a commit that referenced this pull requestJan 9, 2014
…rrorDocument the failed login limit and lockout scope for API
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Labels
None yet
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I recently hit a brick wall developing with the Gists API due to some 404's being returned for the /gists endpoint, not realizing that Github had the concept of scope and that I was missing it.
Staff behindsupport@github.com helped me work through my mistake. This was my bad for not seeing that in the OAuth docs but based on my research of the issue I think [I'm not the only one][1] to have made the error.
I think someday returning something like a 401 "Forbidden" might help clue in developers like myself who skipped over the scope section, but in the meantime I'm hoping this commit might be able to pay back the support cost I incurred Github by preventing others from making my same error.
[1]https://github.com/blog/846-new-issues-and-gist-api#comment-13057