Skip to content
This repository has been archived by the owner on Apr 15, 2019. It is now read-only.

Action required: Greenkeeper could not be activated 🚨 #775

Closed
greenkeeper bot opened this issue Sep 25, 2017 · 0 comments
Closed

Action required: Greenkeeper could not be activated 🚨 #775

greenkeeper bot opened this issue Sep 25, 2017 · 0 comments
Labels

Comments

@greenkeeper
Copy link

greenkeeper bot commented Sep 25, 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.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

@slaweet slaweet added the chore label Sep 29, 2017
@slaweet slaweet closed this as completed Sep 29, 2017
@slaweet slaweet self-assigned this Sep 29, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant