Frequently Asked Questions
- I enabled a repo, but nothing’s happening
- Greenkeeper is creating branches and immediately deleting them again
- I can’t enable a repo that was recently renamed
- I get ERR! enable Couldn’t enable a project with this slug
- Can I enable Greenkeeper on a different branch?
- Can collaborators enable Greenkeeper too?
This might be because the dependency updates are within your specified ranges, and not breaking your tests. So there’s no point in bothering you with a PR, since everything still works.
You’ll only receive pull requests when an in-range dependency breaks your build, or when a dependency updates outside your specified range.Back to top
Greenkeeper tries to get the package from the configured git origin, which is probably using an old slug, from before renaming the repo, for example. GitHub will forward that internally, but we have no way of finding out the repo’s new name.
Solution 1: explicitly pass the repo slug to greenkeeper
greenkeeper --slug=user/repo enable
Solution 2: Update the git config
Update the repo name in .git/config
At this point, there is no configuration setting for the branch, but Greenkeeper picks the default branch that is set up on GitHub for Pull Requests, so that’s a place where you can change it.
We are planning to introduce a more flexible configuration setting in the future and we’ll let you know when it is available.Back to top
Greenkeeper creates branches on your repository to send you PRs, and we need push access to the repository. On top of that we need to create webhooks so we can keep your `package.json` content in sync, which requires admin access.
So no, unfortunately being a collaborator currently isn’t sufficient.Back to top