After everything announced in GitHub Universe and with that to improve the reliability of GitHub overall, yet we have another incident afterwards.
It doesn't matter what GitHub does, only you can decide for yourself to self-host rather than going all in on GitHub and it continues to go down.
Predicted this 6 years ago and self hosting has aged perfectly well. [1]
Takes a few minutes a month to update and babysit. We only basically use the CI and the repository functionality though so gitlab has been "feature complete" for us for a while. Probably I we could swap to something like gitea or forgeo but the gitlab CI seems like a nice balance between powerful when it needs to be and simple otherwise for our use case so there is nothing driving us to swap.
Disclaimer: I am building a code forge myself at https://juju.bi
Github has a decade of positive reputation to deal out, I don't see Grok or OpenAI jumping in and competing with that.
Without free CI in GitHub, you might as well say:
"they can just shut the whole thing down and this reliability issue will be solved immediately"
The federated code forge (https://news.ycombinator.com/item?id=50305573)
https://news.ycombinator.com/from?site=githubstatus.com
It's driven by aggregated user complaints, so it's pretty high-quality. Comment counts are a proxy for "how bad was the outage" + "how long was the outage thread topical for".
After many outages we had to build our own free runner https://github.com/supercorp-ai/superci
I would not be surprised if a serious amount of this usage is not user-intended and instead the LLM just inserts some sort of CI job off the bat and people roll with it.
uneekname•1h ago
jefb•1h ago