Discover GitHub token scope #17
Open
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
|
He @jessfraz, |
|
Hi @kaplanelad, we are not likely to merge this currently. The clients in this repo are specifically generated based on OpenAPI specs (as defined by a given service). I can look in to seeing if there is something in the spec that we could generate this data from. I think for now it makes sense to keep it as a standalone crate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hey,
We often want to know which access the token client has before executing the API request.
I have added a small package called github-scopes-rs, which allows us to get the scope of the token.
This package returns a boolean fields struct (mapped to the GitHub checkboxes permission via the UI).
GitHub Scope Documentation
I have created an example file: