News for hackers. Stuff that matters.
Re:Incident with Pull Requests, Git Operations and Issues by gophigure on Wednesday November 04, 2026 @09:49AM (#50366293)
What I find problematic, especially for teams that rely on GitOps and GitHub being (relatively) stable, is the fact that GitHub's status page can't be relied on. You arrive at the conclusion, "this must be GitHub," but the status page rejects the notion, and so you go digging. That can lead to a lot of toil and wasted time, in addition to sideways looks paired with comments like, "but status shows green."

A sick person with symptoms is clearly sick, but sometimes they're asymptomatic. That's what the GitHub status page has become. When it's red and showing problems, you know you have problems. When it's all green? You know you MIGHT have problems.

That can make outages like this harder to triage, since reality is a black box.

Re:Incident with Pull Requests, Git Operations and Issues by c0rruptbytes on Wednesday November 04, 2026 @10:30AM (#50366997)
I can imagine a lot of people moving to OCI instead of GitOps
Re:Incident with Pull Requests, Git Operations and Issues by stryan on Wednesday November 04, 2026 @10:35AM (#50367071)
OCI layering on top of running systems a la bootc? or OCI as the desired state storage for CM?
Re:Incident with Pull Requests, Git Operations and Issues by stackskipton on Wednesday November 04, 2026 @11:02AM (#50367511)
SRE here, OCI for storing deployment config information, most of time, Kubernetes manifest files/Helm Charts.
Re:Incident with Pull Requests, Git Operations and Issues by stryan on Wednesday November 04, 2026 @11:56AM (#50368367)
Gotcha, that's what I figured but I was still curious. I've got a side-project that was originally designed for traditional GitOps but got OCI support as a feature submission from a user. I've been seeing more usage of the OCI backend these days and originally figured it was a side-effect of the project domain (Podman Quadlets) but maybe it is an over all field shift.
Re:Incident with Pull Requests, Git Operations and Issues by bdsa on Wednesday November 04, 2026 @12:21PM (#50368668)
In the last couple of weeks, I've been moving a deployment stack off ArgoCD pointing at Git, and ended up settling on Flux fetching OCI artifacts from ECR. The artifacts are built and pushed by GitHub Actions. It seems like a nice way to "have GitOps" without needing GitHub to be up all the time.
Re:Incident with Pull Requests, Git Operations and Issues by c0rruptbytes on Thursday November 05, 2026 @01:39AM (#50375927)
I think so, Argo CD appsets are even getting an OCI generator in the next release (3.6)
Re:Incident with Pull Requests, Git Operations and Issues by arccy on Wednesday November 04, 2026 @10:31AM (#50367011)
This is why you ignore everything for at least 30 min before starting to investigate...
Re:Incident with Pull Requests, Git Operations and Issues by jeroenhd on Wednesday November 04, 2026 @10:33AM (#50367045)
Github is fast in updating their status compared to other companies. Amazon has to be bombed, on fire, and in the news before their status page shows anything about any ongoing issues.

I assume these companies have some kind of uptime guarantee in their contracts, because they seems to care more about covering their asses than about informing customers.

Re:Incident with Pull Requests, Git Operations and Issues by giwook on Wednesday November 04, 2026 @12:04PM (#50368474)
Comparing one shitty set of standards to another shitty set of standards… hmm
Re:Incident with Pull Requests, Git Operations and Issues by sleepybrett on Wednesday November 04, 2026 @12:53PM (#50369130)
No they aren't, we can see outages coming 20+ minutes before GH reports them.

We have outages on our books that they never reported even after we ticketed them.

They cook the stats like an inner city police department.

Re:Incident with Pull Requests, Git Operations and Issues by chanux on Wednesday November 04, 2026 @01:25PM (#50369538)
Not fraud from a legal point of view I guess /s
Re:Incident with Pull Requests, Git Operations and Issues by beardedetim on Wednesday November 04, 2026 @05:39PM (#50372482)
Me and a colleague were just ranting about how there's no way in hell Actions has 99.6% uptime but yet that's what their status page says. Maybe it's just bias and I am only remembering the minutes that it's down what feels like every week or multiple times a week. But I'm suspicious of their stats, even if they declare an incident on the status page.
Re:Incident with Pull Requests, Git Operations and Issues by sleepybrett on Thursday November 05, 2026 @01:11PM (#50382316)
I would suggest every enterprise customer that is not keeping track of github downtime and it's effect on their systems and workforce independently for presentation to their sales team every billing cycle for discounts is leaving a lot of money on the table.
Re:Incident with Pull Requests, Git Operations and Issues by deathanatos on Wednesday November 04, 2026 @06:23PM (#50372847)
> Github is fast in updating their status

Github's status page is incredibly slow in comparison to the status page Github themselves used to have, which had several key metrics of various systems that would update in real time, and when they did have a (comparatively rare) outage, would usually have at least one metric going "yeah, something is wrong".

Re:Incident with Pull Requests, Git Operations and Issues by ozyschmozy on Wednesday November 04, 2026 @01:11PM (#50369352)
> "this must be GitHub," but the status page rejects the notion, and so you go digging

Don't know about you but at this point I've learned to recognize and ignore GitHub issues even when they haven't admitted to it yet

Re:Incident with Pull Requests, Git Operations and Issues by defraudbah on Wednesday November 04, 2026 @04:07PM (#50371532)
show me one status page that's reliable, it turned into smoke and mirrors
Re:Incident with Pull Requests, Git Operations and Issues by solyin on Wednesday November 04, 2026 @04:16PM (#50371646)
downforeveryoneorjustme.com is a high level way to gather that data
Re:Incident with Pull Requests, Git Operations and Issues by thwarted on Wednesday November 04, 2026 @05:43PM (#50372518)
Extremely high level, and mainly merely "is the site accessible". However, github having issues with "issues" or "pull requests" is a functionality, not an accessibility, degradation, which can often only be discovered by actually trying to perform the action/use the functionality and comparing the result to he expected result.
Re:Incident with Pull Requests, Git Operations and Issues by spartanatreyu on Wednesday November 04, 2026 @06:20PM (#50372812)
What you're looking for:

Question 1: Is it github, or is it everyone:

Answer: https://downdetector.com/

(If everyone's having issues, then stop. Otherwise, continue below...)

---

Question 2: Is it github?

Answer 2: https://www.githubstatus.com/

Question 3: Why are you lying to me, is it github or not?

Answer 3: https://mrshu.github.io/github-statuses/

(If github is not having issues, then check your local environment. Otherwise, continue...)

---

Question 4: Why is it always github, surely they're not that bad right?

Answer: https://www.dayswithoutgithubincident.com/

(Perhaps its time to consider an alternative to github, or at least a mirror)

Re:Incident with Pull Requests, Git Operations and Issues by chrisjj on Wednesday November 04, 2026 @07:00PM (#50373134)
[delayed]