It seems lately Github is having constant issues, especially with Actions, Webhooks, and Pull Requests.
How are people handling this? At what point does self hosting become preferable?
https://www.githubstatus.com/history
Constant Outages at GitHub
1–4 of 4 posts
Re: Constant Outages at GitHub
#2Why should developer care about this, if it means free time?
Re: Constant Outages at GitHub
#3Why should developer care about this, if it means free time?
Lots of developers use GitHub Actions and as soon as it goes down and you can't push your urgent critical change, then it becomes your problem.
In fact, it means you are losing time and money waiting for GitHub to fix it as it impacts your ability to deploy / update for production.
Regardless, you should expect GitHub to go down or have an incident every month. It is that unreliable.
Re: Constant Outages at GitHub
#4Why should developer care about this, if it means free time?
Lots of developers use GitHub Actions and as soon as it goes down and you can't push your urgent critical change, then it becomes your problem. In fact, it means you are losing time and money waiting for GitHub to fix it as it impacts your ability to deploy / update for production. Regardless, you should expect GitHub to go down or have an incident every month. It is that unreliable.
Did you consider the idea that for some users it's quite acceptable? I'm perfectly fine with 85% or event 70% availability of Github features since I don't pay a single penny for it. If I had aimed for 100%, I'd probably host and manage tools on my own, without sharing resources and being dependent on someone else's services.