trap failed authentication #41
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
|
lgtm |
|
thanks! merging |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
about half a dozen times i've found myself in a situation where GitHub rejects the token that is passed when attempting to tag a release. this PR just traps the problem and points the user in the right direction to clear their existing config file.
i haven't been able to determine the root cause, and i don't know if its likely to occur again now that you've moved to using
ghauthbut if i'm not the only one it would be a lot cooler for gh-release to trigger a fresh prompt to allow the user to authenticate. i just couldn't figure out how to do it.