Skip to content
This repository has been archived by the owner on Oct 14, 2021. It is now read-only.

Action required: Greenkeeper could not be activated 馃毃 #50

Closed
greenkeeper bot opened this issue Feb 19, 2019 · 0 comments
Closed

Action required: Greenkeeper could not be activated 馃毃 #50

greenkeeper bot opened this issue Feb 19, 2019 · 0 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Feb 19, 2019

馃毃 You need to enable Continuous Integration on Greenkeeper 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鈥檛 receive a CI status on the greenkeeper/initial branch, it鈥檚 possible that you don鈥檛 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鈥檚 configured. Make sure it is set to run on all new branches. If you don鈥檛 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鈥檒l need to re-trigger Greenkeeper鈥檚 initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

@smnis smnis added this to To do in Winter Vacation Feb 19, 2019
@greenkeeper greenkeeper bot closed this as completed Mar 2, 2019
Winter Vacation automation moved this from To do to Done Mar 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Development

No branches or pull requests

0 participants