[bob1029]

This has gotten to a point where it doesn't really matter anymore. When a service crosses a certain reliability threshold it's like a phase change. The customer base eventually adapts to the situation. Anyone who still genuinely cares has moved to self hosted enterprise or something else by now. It was most tenuous for me when they almost met the SLA. Now that they've blown so far beyond it, the stress is mostly gone.

[JsonDemWitOster]

I care but I can't move out because it's Orders from Up High which migrated us to Github. We haven't been here a year and it's not worth my neck to mirror our code in some kind of skunkworks forge instance. Woe. Woe is me.

[exhilaration]

Our Big Giant Enterprise wants to move all our repos from ADO to GitHub for all the nifty AI features, but I'm told the frequent downtime is a major issue so we're slow-walking the migration.

[kelseydh]

We have so many automated workflows and pipelines moving through Github Actions + other Github integrations it would be a giant headache to migrate. Not clear where we would go either. Gitlab??

[SOLAR_FIELDS]

I’ve been running an SMB trending mid market out of gitlab for the greater part of a year with no issues. One of my favorite benefits is that ci runners are colocated with the self hosted instance on k8s so suddenly a whole huge slew of shit that you had to care about with GitHub, security, provenance and supply chain is just… not an issue.

Getting off the GitHub actions dependency is a feature, not a bug

[PeterStuer]

Of course. Every non trivial migration is a 'headache'. But so is being down too many times.

At the very least explore and prepare for alternatives. Map out dependencies that are not trivial to replace. There's probably fewer of those than you think.