-
Notifications
You must be signed in to change notification settings - Fork 2
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 🚨 #1
Comments
Is this repo actually in use? 😱 |
Marketing bot? |
@SamMolokanov the front enders are adding Greenkeeper to all our frontend repos (ie. including a package.json file). It will help us keep dependencies up to date. However we are finding a lot of deprecated repos in the process :) |
@dbackeus archeology is a funny science :) |
Kill it with 🔥 |
😭 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🚨 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.The text was updated successfully, but these errors were encountered: