feat(manual_webhooks): optionally removes need for admin scope

[boennemann]

Closes #46, requires greenkeeperio/website#18.

[phillipj]

Updated to v2.13.0 and followed the instructions described in https://greenkeeper.io/manual-webhooks.html wo/luck.

nodejs/nodejs.org is obviously not a private repo, but the nodejs org doesn't provide access to 3rd party GitHub applications.

On thing that comes to mind when going through the manual-webhooks setup mentioned, is greenkeeper signup --force --no-admin seems odd when I already have linked greenkeeper with my GitHub account. Tried doing login --force --no-admin as well, but still didn't get to enable the nodejs.org repo.

@boennemann any thoughts on what I'm doing wrong here?

[boennemann]

Hey @phillipj,

sorry about this. First of all signup and login are just aliased. I'll update the website to avoid confusion.

Secondly it looks like we're having a problem downgrading your Greenkeeper scope (be aware that there is only one scope for all of your orgs, so if you want to downgrade the scope just for nodejs creating a bot account might be a better idea).

If you want to downgrade the scope for your account would you mind trying gk access and then revoking the Greenkeeper application completely? After that greenkeeper login --force --no-admin should work.

We're working on a fix to do that automatically in the meantime.

Best,
Stephan

[phillipj]

Thanks for answering quickly! I'll try those steps tomorrow morning.

On Sunday, 5 June 2016, Stephan Bönnemann [email protected] wrote:

Hey @phillipj https://github.com/phillipj,

sorry about this. First of all signup and login are just aliased. I'll
update the website to avoid confusion.

Secondly it looks like we're having a problem downgrading your Greenkeeper
scope (be aware that there is only one scope for all of your orgs, so if
you want to downgrade the scope just for nodejs creating a bot account
might be a better idea).

If you want to downgrade the scope for your account would you mind trying gk
access and then revoking the Greenkeeper application completely? After
that greenkeeper login --force --no-admin should work.

We're working on a fix to do that automatically in the meantime.

Best,
Stephan

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#205 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABLLEzzDdEaGupBquMS5T7P9WWtnqVf5ks5qIztwgaJpZM4IuVYM
.

[phillipj]

@boennemann sadly revoking and logging in again had no effect. Still the same error when trying to enable nodejs.org. Anything else I can do on my end which helps you debug this?

[lpinca]

@phillipj did you try with a new bot account?

[phillipj]

@lpinca nope. I'll try with the nodejs-github-bot account

On Saturday, 11 June 2016, Luigi Pinca [email protected] wrote:

@phillipj https://github.com/phillipj did you try with a new bot
account?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#205 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABLLE2qJa_mbO8TewbaeZcsKAmm1izLTks5qKmUegaJpZM4IuVYM
.

[phillipj]

No luck using the nodejs-github-bot account either :( That account has never been used with greenkeeper before, so having to downgrade the account should not relevant.

@boennemann you know anyone who has "no admin" up-n-running?

[lpinca]

@phillipj can we try again?

[phillipj]

@lpinca sure 👍

This is what I see when trying to install the Greenkeeper integration:

Sadly the nodejs organization doesn't show, probably because I'm not an organization owner. Possibly something @Fishrock123 can give a shot?