If I remember it well, every once in a while a new cool feature was also breaking stuff, doubling the chances of getting to the top page here. But truth being told, GitHub was fixing those at light speed too and it was very interesting to follow their progress. Their delivery pipeline (per branch, deliver when ready, etc.) sounded very much innovative by then and I think inspired many people.
We use GitLab on the daily. Roughly 200 repos pushing to ~20 on any given day. There have been a few small, unpublished outages that we determined were server side since we have a geo-distributed team, but as a platform seems far more stable than 5-6 years ago.
My only real current complaint is that the webhooks that are supposed to fire in repo activity have been a little flaky for us over the past 6-8 months. We have a pretty robust chatops system in play, so these things are highly noticeable to our team. It’s generally consistent, but we’ve had hooks fail to post to our systems on a few different occasions which forced us to chase up threads until we determined our operator ingestion service never even received the hooks.
My org hosts it on prem, and while I don't like the way pages are organized for projects, I only really interact with the PR page and that is laid out well. Most of my interaction with git is happening from my terminal anyway so ¯\_ (ツ)_/¯
I still can't pull new branches even though the incident says it's resolved. I don't think my boss would be happy with me taking a break this long... but what else can I do when our business uses GH?
There were so many severe Github Actions outages (10+ ?) in the past year. Cause: Migration to the disaster zone also known as Azure, I assume. Most of them happened during (morning) CET working hours, as to not inconvenience the americans and/or make headlines.
Money doesn't buy competency. It's a long-term culture thing. You can never let go on maintaining competency in your organization. It rots if you do. I guess Microsoft did let go.
Hey, I'm the GitHub employee who's working on fixing that right now. The service powering those stats is _ancient_, and it fell over back in September. It's taken longer than I hoped to get a replacement working, but it should be fixed within the next couple of weeks, fingers crossed.
Speaking of "temporarily unavailable but it's actually forever", I've been wanting to get into Fallout and Starfield modding, so been waiting for their official wiki to come out of maintenance mode. I think I first tried to access it when Starfield launched (September 2023), and still today it is "currently down for backend maintenance". https://wiki.bethesda.net/
I really do feel for those hubbers that are still working on this years into the Microsoft era. GitHub was an excellent product and from what I hear it was an excellent culture too. I can only assume the culture has eroded similarly to the product itself as Microsoft has finally begun integrating the org into the slower moving machine that is MS.
Doubt it. I'm Ops person on Azure, while they just had terrible outage recently, they tend to be as stable as any other cloud provider and I haven't had many issues with Azure itself compared to whatever slop the devs are chucking into production.
Yep. Was using github for oauth on a petproject of mine. Got the unicorn, and was considering takingthe break, or just etting up something else. Seems to be running again for me now though.
We used to obsessively care about 500s. Like I would make a change that caused a 0.1% spike in 500s and I would silently say I'm sorry to the folks who got the unicorn page.
I'm not sure the new school cares nearly as much. But then again this is how companies change as they mature. I saw this with StubHub as well.. The people who care the most are the initial employees, employee #7291 usually dgaf
theletterf|3 months ago
no_wizard|3 months ago
arnvald|3 months ago
alentred|3 months ago
numbsafari|3 months ago
We originally left GitLab for GitHub after being bit by a major outage that resulted in data loss. Our code was saved, but we lost everything else.
But that was almost 10 years ago at this point.
kaishiro|3 months ago
My only real current complaint is that the webhooks that are supposed to fire in repo activity have been a little flaky for us over the past 6-8 months. We have a pretty robust chatops system in play, so these things are highly noticeable to our team. It’s generally consistent, but we’ve had hooks fail to post to our systems on a few different occasions which forced us to chase up threads until we determined our operator ingestion service never even received the hooks.
That aside, we’re relatively happy customers.
boilerupnc|3 months ago
[0] https://status.gitlab.com/pages/history/5b36dc6502d06804c083...
geoffbp|3 months ago
colesantiago|3 months ago
Haven't seen any outage from GitLab in like, ever.
ctkhn|3 months ago
arccy|3 months ago
hoherd|3 months ago
ecshafer|3 months ago
isodev|3 months ago
PS: None of our 40+ engineers felt anything, our self hosted Forgejo is as snappy as ever.
cube00|3 months ago
lysace|3 months ago
There were so many severe Github Actions outages (10+ ?) in the past year. Cause: Migration to the disaster zone also known as Azure, I assume. Most of them happened during (morning) CET working hours, as to not inconvenience the americans and/or make headlines.
Money doesn't buy competency. It's a long-term culture thing. You can never let go on maintaining competency in your organization. It rots if you do. I guess Microsoft did let go.
unknown|3 months ago
[deleted]
JLCarveth|3 months ago
prymitive|3 months ago
“ Referring sites and popular content are temporarily unavailable or may not display accurately. We're actively working to resolve the issue.”
It’s been like that for months now with no sign of anyone working on it. They just don’t care about user experience anymore.
https://github.com/orgs/community/discussions/173494
vaindil|3 months ago
embedding-shape|3 months ago
_heimdall|3 months ago
contravariant|3 months ago
pfyra|3 months ago
spockz|3 months ago
danfritz|3 months ago
drcongo|3 months ago
the_af|3 months ago
bob1029|3 months ago
stackskipton|3 months ago
Fokamul|3 months ago
nkzd|3 months ago
coffeebeqn|3 months ago
dustfinger|3 months ago
zamalek|3 months ago
FrostKiwi|3 months ago
unknown|3 months ago
[deleted]
gkoberger|3 months ago
dustfinger|3 months ago
gunalx|3 months ago
marak830|3 months ago
rvz|3 months ago
Are they using AI agents this time to resolve the outage? Probably not.
But this time, there is no CEO of GitHub to contact and good luck contacting Satya to solve the outage.
stuffn|3 months ago
carlyai|3 months ago
whoknowsidont|3 months ago
Scribesley|3 months ago
[deleted]
unit149|3 months ago
[deleted]
fishgoesblub|3 months ago
wavemode|3 months ago
Any time their startup competitors are making too much progress they can just push the "GitHub incident" button and slow everyone down.
grepfru_it|3 months ago
I'm not sure the new school cares nearly as much. But then again this is how companies change as they mature. I saw this with StubHub as well.. The people who care the most are the initial employees, employee #7291 usually dgaf