"Actions, Issues" are not "Git operations".
would sound better without "other" in title
GitHub incident: ongoing issues with Actions, Issues and other Git operations
41–50 of 130 posts
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#42Wondered why I couldn't push my notes, appears that pushing commits is also impacted.
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#43Cannot create a new repo
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#44Wondered why I couldn't push my notes, appears that pushing commits is also impacted.
Goddamn and here I thought I was getting errors because the files i pushed were to large or something.
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#45CivitAI.com is down and Hugging Face is having 502s for some operations. Perhaps there is a larger issue?
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#46Earlier quoted context omitted.
https://www.githubstatus.com/history lists 72 incidents since January
The point isn't that GitLab has more, the point is that running these things at global scale is pretty complicated, and everyone has problems. "Just switch to GitLab" is pithy but isn't in itself an actual solution.
You can self-host GitLab and have few, if any, incidents that get resolved very quickly. Worked for a company that had no incidents that I observed in ~3 years, now work at a company that had ~2 incidents in 1.5 years.
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#47I debugged for one min at 11:59 trying to push, and then my eat-lunch notification came in at 12:00 and I opened hackernews with a tuna sandwich and this is super helpful because it means I wont need to debug it locally for 10 mins before figuring out Github is down.
Edit - Just want to clarify when I say "opened hackernews with a tuna sandwich" I want to clear up that I did indeed full on mash the keyboard letters with my sandwich. It's costing me a fortune in keyboards every day and it's ruining my sandwich most days as well, I think I have an issue.
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#48Why don't we all collectively mirror our repos to gitlab and switch development to there during the monthly outage?
Feature mismatch of anything outside Git. And no one wrote the tooling needed to synchronize issues, pull/merge requests, ... back and forth.
Even so, for a lot of devs its still easier as a temporary collaboration point than sending patches via mail.
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#49Interested to hear whether anyone actually managed getting some Client Credits as per their SLA [1]? Over the last quarter they probably went sub 99.9% in some services.
[1] https://github.com/customer-terms/github-online-services-sla
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#50I debugged for one min at 11:59 trying to push, and then my eat-lunch notification came in at 12:00 and I opened hackernews with a tuna sandwich and this is super helpful because it means I wont need to debug it locally for 10 mins before figuring out Github is down. Edit - Just want to clarify when I say "opened hackernews with a tuna sandwich" I want to clear up that I did indeed full on mash the keyboard letters w…
Ideally both GitHub and HN would be down at the same time. With nowhere to discuss the former, people might actually get something done.