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

Action required: Greenkeeper could not be activated 🚨 #1

Closed
greenkeeper bot opened this issue Sep 29, 2018 · 0 comments · Fixed by #3
Closed

Action required: Greenkeeper could not be activated 🚨 #1

greenkeeper bot opened this issue Sep 29, 2018 · 0 comments · Fixed by #3

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Sep 29, 2018

🚨 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 it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

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

Once you have installed and configured CI on this repository correctly, 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 App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

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

Successfully merging a pull request may close this issue.

0 participants