This repository has been archived by the owner on Jul 12, 2022. It is now read-only.
Adding user:email to personal token scopes #1038
Merged
Conversation
This file contains 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
NuKeeper fails for me without this
|
I don't know why but for me the docs still not say user:email is a required scope. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adding user:email to personal token scopes
✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)
Website update
When adding only the recommended scopes and then running NuKeeper, I get the error "NuKeeper.Abstractions.NuKeeperException: user/emails was not found."
🆕 What is the new behavior (if this is a feature change)?
NuKeeper succeeds
💥 Does this PR introduce a breaking change?
No
🐛 Recommendations for testing
N/A - documentation only
📝 Links to relevant issues/docs
N/A
🤔 Checklist before submitting