Closed greenkeeper[bot] closed 6 years ago
Same as #5
Kinda clueless how to get this sorted.
I hope @mAiNiNfEcTiOn comes back to our org (invite still pending), since he is such a pro at handling service integrations š¬ . FrintJS needs him!
@fahad19 I don't have access to the settings page ...
@mAiNiNfEcTiOn: thank you for coming back! you are an Owner just like before again š
@fahad19 not in the frint-props which is the one that I should have to help here. š
@mAiNiNfEcTiOn: oops sorry. this repo didn't have any assigned team. I just added 'Core' team to it as admin. everyone in the team should have access now for this repo.
Closing it as done.
šØ 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.