bot suddenly stopped merging

[dareojo]

Probot auto merge suddenly stopped working today.

Kindly advise. Nothing has changed in the Repository..

Thank you

[bobvanderlinden]

You're absolutely right. There was a problem after upgrading to a new version of probot. It should be resolved now.

[dareojo]

It is still not auto-merging. Is there anything I have to do from my end? It started since yesterday

[ostrolucky]

It merged last PR for us 22 Aug 2019, 07:50 CEST, but PR where we applied label 22 Aug 2019, 08:17 CEST was not picked up

[dareojo]

It has stopped again :( Is there a way to make it work continuously and seamlessly?

[bobvanderlinden]

I've tried to fix the issues a few times. There were a few after upgrading to a new probot version. Those issues should've been resolved. In addition, I needed to do a few restarts of the Heroku instance. Every time that happens there is a chance PRs are skipped.

Please do note that probot-auto-merge is running on a free instance of Heroku, a single dyno. You may host your own if you'd like a potentially more stable solution.

[dareojo]

Thanks for the response. Does it update automatically? Do you have steps for hosting it on our own heroku instance and creating a github app from it?

[bobvanderlinden]

yes it usually deploys automatically on commits on master, but because of the problems (and automatic merging of dev dependencies), I temporarily disabled that process.

For hosting your own probot, please see https://probot.github.io/docs/deployment/
It will not automatically update. You need to do your own testing / staging environment to make sure the bot runs stable on production.

[bobvanderlinden]

Unfortunately I've hit the limit of my free tier on Heroku today ☹️. I will probably pay for this month, but need to look into sponsorship.

[shepting]

@bobvanderlinden Could I Venmo you some money to help with the hosting costs? Ideally, in exchange you could get the nixpkgs-ruby working inside a nix-shell environment? bobvanderlinden/nixpkgs-ruby#1