undefined | Better HN

0 pointsagartner17d ago0 comments

There was another really bad incident today: https://www.githubstatus.com/incidents/zsg1lk7w13cf

> We have resolved a regression present when using merge queue with either squash merges or rebases. If you use merge queue in this configuration, some pull requests may have been merged incorrectly between 2026-04-23 16:05-20:43 UTC.

We had ~8 commits get entirely reverted on our default branch during this time. I've never seen a github incident quite this bad.

0 comments

nulltrace17d ago

Downtime is one thing. Silently reverting commits on your default branch is something else entirely.

darknavi17d ago

Similar here. Somewhat ironic that a tool that was supposed to be preventing merge conflicts was authoring completely mangled commits to our mainline branch.

lucasqueiroz17d ago

We've also seen quite a few commits disappear from main, the status of the PRs continued on merged. Was stressful.

robertwt717d ago

yeah this is crazy we had many PRs reverted as well on many repos. downtime is 1 thing, but reverting PRs is failure on another level

CoastalCoder17d ago

Really makes one appreciate that concept of A.C.I.D. database transactions.

olingern17d ago

Same, we got an email with a PDF with the affected commits and how to fix. What an absolute clown show.

j / k navigate · click thread line to collapse