semantic-pull-requests: semantic PR check still not working

Also still seeing this issue, though somewhat intermittently. Very strange!

Looking better so far!

Hey folks. Sorry to hear it. I haven’t made any changes so I’m not sure what’s up here. I will try to investigate today.

In the meantime if you’re blocked, I’d suggest standing up your own instance of this app, or using a GitHub Action to do your semantic PR checks. See the README of this repo for more details about that.

Hey folks. Thanks for being polite and trying to help discover the source of the issue. I took a look at the Heroku app that’s running this service today, and it’s just been falling over a lot, presumably from increased usage, as no changes have been made to the app itself recently.

I went ahead and bumped it from a Hobby Dyno to a Standard 2X, which has more memory, CPU share, and “compute”.

Let’s see if that helps. 🤞🏼

For posterity, here’s a snapshot of recent app metrics:

@dev-nicelee Please reopen this issue as this is sporadic.

Going over the code, it doesn’t seem like an issue with the code itself, but rather an issue with actually running this bot.

However, there doesn’t seem to be any way to debug GitHub checks…

Thanks for reporting @guilhermetod – this should be fixed now.

It was a Node.js upgrade that passed CI but failed in production: https://github.com/zeke/semantic-pull-requests/pull/177

Experiencing this hanging now

Haven’t had any issues so far! @zeke

Looks to be working now

Good to hear. Working for others too? I didn’t change anything.

Thanks for that bit of info @pamelasarkisyan… I didn’t realize the release process was broken. semantic-release is a bit finicky.

I’m not sure releases are really related to this issue though, as the hosted version of this app is deployed to Heroku whenever the default git branch is updated. 🤔