-
Notifications
You must be signed in to change notification settings - Fork 34
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
Workaround for failing ghrelease activity due to changes to device flow auth #259
Comments
@scopatz @CJ-Wright could someone enable that feature? |
@CJ-Wright @saraedum is that something one of you could do? Following the above instructions works just fine for me but it requires modifying the I think creating a GH app for the |
Also simply updating the current GH app by checking "Enable Device Flow" should be enough. |
Let me look into this today. |
I had this same issue, it hasnt been fixed yet |
@sbillinge have you been able to fix that? |
I don't think I have the permissions to change that application @CJ-Wright |
The application seems to be owned by @regro so we would need help (or permissions) from one of @xhochy, @ocefpaf, @isuruf, @CJ-Wright, @marcelotrevisani probably. |
I don't have enough rights here |
Same. |
Which GH app is this exactly? Is this the regro-bot app? @beckermr I think you may be the last person to work on that app. I am making this comment solely in my personal capacity and am not conveying any rights to any intellectual property of any third parties. |
Wasn't me. |
@wolfv @mariusvniekerk are you aware of the regro-bot? Is that being used for CF things or is this a rever thing? (Sorry for the additional delay, just trying to do all due diligence before making changes to a potentially communal resource) I am making this comment solely in my personal capacity and am not conveying any rights to any intellectual property of any third parties. |
Now I found the right app. I think you should be good to go. Email is the best way to reach out to me these days. Cheers, I am making this comment solely in my personal capacity and am not conveying any rights to any intellectual property of any third parties. |
GitHub now returns 400s if you try to login via an oauth app for device flow if the oauth app in question has not checked the "Enable device flow" option.
I don't know who currently owns the
rever
oauth app that is used, but if you are blocked by this, you can work around it by creating your own.Go to https://github.com/settings/applications/new
Give it a name, the callback url can be anything (like
http://localhost
) since it won't be used.Then check "Enable Device Flow" and save the app.
Copy the "Client ID" of your new app and paste that into rever/github.xsh around line 44 and replace the listed client id for
REVER_CLIENT_ID
.Then the login flow should work to authorize the device
The text was updated successfully, but these errors were encountered: