-
Notifications
You must be signed in to change notification settings - Fork 96
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
Enable Greenkeeper without repo admin access #68
Comments
Just found out we don't allow private access to third-party applications anymore, might that be causing these issues? We're seeing some similar issues with our Travis integration these days.. |
might be a similar issue - i have a private repo where greenkeeper creates branches but it does not make PRs. how do i fix that? |
@jonathanong is your case also with fixed version numbers? If you use ranges, we only open PRs when the build breaks. @phillipj that might well be possible. We’ll realistically investigate more thoroughly after the holidays. Thanks for your patience! |
@janl ah that must be it. thanks. |
Thanks @janl, much appreciated! Happy holidays 🎄 |
@janl we'd still love to use greenkeeper.. Have you figured out if you require private access for it to work? |
@phillipj oops, sorry, I skimmed issues and thought this was resolved, while it really isn’t yet! We’ll be able to help you very soon, stay tuned! :) |
Oooh, sounds good! Thanks for the update 👍 On Friday, 6 May 2016, Jan Lehnardt [email protected] wrote:
|
sorry for closing this issue again, but this is a duplicate of #46 😊 |
This landed with Details: https://greenkeeper.io/manual-webhooks.html Thanks for your patience. |
Awesome, thanks! |
cc: @Fishrock123 @mikeal |
Is there any action I need to take here? |
@Fishrock123 I don't think so, @phillipj tried to make it work with no luck so far. |
@lpinca Right, I was asking if there is something concrete we (node.js owners) need to do permissions-wise to help this? |
Oh, sorry. |
Any tips on debugging missing greenkeeper PRs?
As raised by @lpinca in nodejs/nodejs.org#355 (comment), we're missing a PR on nodejs.org about
node-version-data
latest patch about 11 hours ago in rvagg/node-version-data@41c3d5b. It's specified with an exact version in our package.json, so it should always create a PR for any new version, right?The text was updated successfully, but these errors were encountered: