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 🚨 #1

Open
greenkeeper bot opened this issue Oct 31, 2018 · 6 comments
Open

Action required: Greenkeeper could not be activated 🚨 #1

greenkeeper bot opened this issue Oct 31, 2018 · 6 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Oct 31, 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.

@dbackeus
Copy link

Is this repo actually in use? 😱

@SamMolokanov
Copy link

Marketing bot?

@dbackeus
Copy link

@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 :)

@SamMolokanov
Copy link

@dbackeus archeology is a funny science :)

@ewal
Copy link
Contributor

ewal commented Oct 31, 2018

Kill it with 🔥

@himynameisjonas
Copy link

😭

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

No branches or pull requests

4 participants