Perhaps you should actually consider self-hosting? [0] As I said and predicted years ago? [1]
But as expected [2] every month, there is an incident and something at GitHub breaks and goes down. Maybe GitHub is gradually falling apart.
It is that unreliable.
[0] https://news.ycombinator.com/item?id=36526334
Github is down a few hours per month but it has never lost data. Work doesn't grind to a halt because your git host is down. So really, Github still provides a lot more value than self hosting.
But sure, keep evangelizing and talking down to people who prefer it to self-hosting, I'm sure it will accomplish your goal.
> Work doesn't grind to a halt because your git host is down.
When you cannot push your critical change to master on GitHub or run your GitHub Action, then it does grind work to a halt, as it has done with the many commenters here.
> So really, Github still provides a lot more value than self hosting.
Centralizing everything to GitHub is much more riskier than self-hosting given the number of times GitHub has fallen over or had an 'incident'.
> But sure, keep evangelizing and talking down to people who prefer it to self-hosting, I'm sure it will accomplish your goal.
My point is self-proving every month and week that something in GitHub goes down or has an incident. I'll be expecting you to complain again once it falls over in a month's time at the latest.
I've been an incident responder where the incident was, "We promised a customer that changes would go out today, but GitHub is down, and thus our CI/CD is also down."
It definitely does matter when GitHub goes down.