-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error message didn't clearly indicate when missing PAT #21
Comments
cc: @ateucher |
Hope you don't mind me jumping in: I think the issues is not that it failed, but that the error message didn't indicate an authentication error, which it likely was. Perhaps the error messages from the failures captured with |
thanks @ateucher , yes that is correct! |
Thank you both! I agree regarding improving the error message. I also need to add a mention of |
That code for guessing what type of thing an username is really really wonky. |
Actually I've now simplified the code so errors will come from gh directly: this way the user will see 401 and 404. Could you please have a look at #24? Thanks again for reporting the bug. |
Yup, that makes perfect sense to me @maelle! Thanks for the quick fix! |
+1, Thank you so much @maelle ! |
Awesome, thank you for reviewing and thanks again for reporting! |
Hello! Thanks for this package, it is really super to have and use.
It is now working for me after I inspected my account and created a PAT.
Previously, when I only had one expired PAT in my account, I got the following error message:
[that is the full error, not truncated].
I don't have a reproducible example, and like I said above, I was able to inspect and update my PAT, but I wanted to share for awareness. Thank you!
The text was updated successfully, but these errors were encountered: