-
Notifications
You must be signed in to change notification settings - Fork 21
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
Github client panic v1.3.0 #94
Comments
Sorry for being so crashy! This is an intereseting one. Your token didn't fail to get a user, but also didn't get a user. Interesting! We can make this safer, but I assume that it'll fail to checkout code, as git won't have a name or email address. What kind of token are you using? |
Its using a classic PAT, with no admin privs. Previous versions complained about not getting email during the github client initialization, but would continue to function. Seems like it may be required now. |
Ah here we go - the account now needs its email address displayed publicly. |
Is there any way to use v1.3.0 without a public email address? |
Yeah, that was unintentional. Working on the fix now |
@audrey-mux would you mind testing the image in #95 and see if that resolves your panic? |
Looks like it does resolve the issue :-)
|
Hey guys
Just pulled v1.3.0 (new app capability, yay!) - hitting this during pod startup.
sorry for being so annoying :-)
The text was updated successfully, but these errors were encountered: