-
Notifications
You must be signed in to change notification settings - Fork 95
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
Manual webhooks setup, removes admin scope #46
Comments
Any progress on this by any chance? We're struggling with getting greenkeeper up-n-running on nodejs/nodejs.org#377 and would really appreciate if we could add these webhooks manually. |
I'd also really like to see this feature land. I am struggling because greenkeeper requires a lot of permissions (write access to all public repositories is a lot to ask). Being able to setup webhooks manually and being able to avoid these broad permissions would be great. Now that I am writing this: Why does greenkeeper need write access to repositories? I can understand the webhooks part… |
Having this would be great. I am a member of several organisations that let anything have access to all their things. I don't want greenkeeper to have access to 100s of repositories in my orgs when all I want to do is add greenkeeper to a personal project. Having a webhook would be great. I know this will be implemented and am not asking anyone to rush, just giving an anecdote :) |
This landed with Details: https://greenkeeper.io/manual-webhooks.html Thanks for your patience. |
Is there some way to set up the new version of Greenkeeper without granting admin scope by manually setting up the webhooks? |
This is technically doable, but requires some extra implementation bits to keep it secure.
Worthwhile feature for sure.
The text was updated successfully, but these errors were encountered: