[gen220]

FWIW, GitHub is also unreliable with webhooks. Many recent GH outages have affected webhooks.

They are pretty good, in my experience, at *eventually* delivering all updates. The outages take the form of a "pause" in delivery, every so often... maybe once every 5 weeks?

Usually the outages are pretty brief but sometimes it can be up to a few hours. Basically I'm unaware of any provider whose webhooks are as reliable as their primary API. If you're obsessive about maintaining SLAs around timely state, you can't really get around maintaining some sort of fall-back poll.

[cmckn]

> you can't really get around maintaining some sort of fall-back poll.

This has been my experience with GitHub Actions as well, which I imagine rely on the same underlying event system as webhooks.

Every so often, an Action will not be triggered or otherwise go into the void. So for Actions that trigger on push, I usually just add a cron schedule to them as well.

[kaishiro]

Completely agree on all points. We've had dual remotes running on a few high traffic repos pushing to both GitLab and GitHub simultaneously as a debug mechanism and our experiences mirror yours.