Skip to content
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

Action required: Greenkeeper could not be activated 🚨 #25

Closed
greenkeeper bot opened this issue Jun 14, 2017 · 2 comments
Closed

Action required: Greenkeeper could not be activated 🚨 #25

greenkeeper bot opened this issue Jun 14, 2017 · 2 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Jun 14, 2017

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

@espy
Copy link

espy commented Jul 11, 2017

Hi @joshperry, Alex from Greenkeeper here, we’re looking into what might have happened here, sorry for all the undue 🚨 and for it not working out of the box.

I saw that you gave Greenkeeper permission to work on this repo again, and that it’s opened it’s initial PR here. Since all dependencies were up to date, the repo is automatically enabled and GK will now send you PRs when dependencies break your build, nothing else to do there.

If you want your lockfile to be updated as well, there’s an extra step that Travis needs to perform for you.

If you have any more questions or issues, just reply to me here and I’ll get back to you.
All the best from Berlin,
Alex

@joshperry
Copy link
Contributor

Hi @espy,

Thank you for the follow up!

I did disable the integration then reeanable it. I saw this recommended @ greenkeeperio/greenkeeper#432 and it seems to have resolved the issue.

Let me know If there's any info I can offer to assist in hunting this sporadic issue down.

Josh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants