greenkeeperio
Action required: Greenkeeper could not be activated for repo without CI
Got 6 issues from the bot for a bug repro repo.
https://github.com/SimenB/webpack-circular-invalid
Hey @SimenB,
thank you for reporting this. It looks like you tried to enable Greenkeeper 6 times in a row, which resulted in us creating 6 of these issues.
Can you confirm that you tried to enable (and disable) Greenkeeper repeatedly from the Integrations settings? Otherwise I'd investigate if there is another explanation for this.
Best, Finn
I have not touched the integration in months. It's been active since maybe a couple of days since you made it available.
This looks like #432. I have the same problem. See derhuerst/asciicast-read-stream#1 and derhuerst/algorithmic-vomit#1 for the most recent ones.
we haven’t gotten other reports about this. Please re-open if this happens again.
It happened again at the beginning of June this year for me:
https://github.com/SimenB/available-cpu/issues?utf8=%E2%9C%93&q=is%3Aissue
Te five times might point to our retry logic, but that would be weird, as we only do that on errors. We should check if this coincided with any GitHub API outages.
I just had 7 issues opened yesterday (after creating a new repo with greenkeeper enabled for all repos). You can see the issues created here: https://github.com/YoloDev/rollup-config/issues?q=is%3Aissue+is%3Aclosed
