GitHub outages are very reliable, as I live in Europe and they always come in the afternoon they're a great reminder to go get lunch
It's a feature, not a bug!
Incident with Issues and Pull Requests
71–80 of 143 posts
Re: Incident with Issues and Pull Requests
#72Earlier quoted context omitted.
Gitea's ability to create a local repository as mirror of a remote repository is great for this. You can stay on Github and have your code regularly mirrored locally.
If only Git had this sort of functionality built in…
Pretty sure git can not continuously pull/push the mirrored repo like this feature does, by default every 10 minutes.
Re: Incident with Issues and Pull Requests
#73Does anyone host their own git repos in an enterprise environment? How do you do it and what are some good resources for learning how to do this?
At a previous employer we used gitea along with jenkins.
Re: Incident with Issues and Pull Requests
#74What is going on over there? Third day in a row is... kind of impressive.
They blamed the march and april outages on some database query that was changed due to an infrastructure change they rolled out. I'm guessing their infrastructure change caused some other race condition issue that they are only seeing after major production failure due to not load testing enough in their staging environment https://github.blog/2023-05-03-github-availability-report-ap...
As much as I’ve been frustrated by these outrages, we’ve all been there
Re: Incident with Issues and Pull Requests
#75Anecdotal - I've been using Gitlab for a few years on some projects, and haven't experienced any downtime issues with them of this magnitude.
Yeah, Gitlab has had its share of downtime. Github has had shockingly little until the last year or two. These things come and go. Of course, if this continues happening it may be time for the OSS community seriously consider migrating en masse. [Edit to fix grammar - thanks for the corrections!]
FWIW the typical phrase is "en masse" (which is French). The English translation is "in mass".
Re: Incident with Issues and Pull Requests
#76Anecdotal - I've been using Gitlab for a few years on some projects, and haven't experienced any downtime issues with them of this magnitude.
Yeah, Gitlab has had its share of downtime. Github has had shockingly little until the last year or two. These things come and go. Of course, if this continues happening it may be time for the OSS community seriously consider migrating en masse. [Edit to fix grammar - thanks for the corrections!]
Apologies to be pedantic, I think it's en masse.
Re: Incident with Issues and Pull Requests
#77Re: Incident with Issues and Pull Requests
#78Earlier quoted context omitted.
Feels like an organization as big as Microsoft must surely have some sort contingency plan in place before doing such a large migration. Right?
Sales handing out Office365 discounts and trying to convince people that AWS and GCP is going to steal their data, judging by companies I worked for that used Azure.
Wasnt it true? Thas Amazon abused their AWS position and stole their competitors data, so thats why Germany's retail businesses are building their own Clouds
Re: Incident with Issues and Pull Requests
#79This gives me some the fail-whale vibes. But the blue bird didn't fail like this these days, strangely.
Re: Incident with Issues and Pull Requests
#80I'm going to self-host my git repos. Any recommendations?
The git+nginx would suffice but it does not offer GUI. I need one to see the changes proposed (aka PRs).
Gitea is nice, but a bit overkill for my needs. I don't need CI, files hosting, issues, team members, releases, wiki, forking/watching/staring, etc.