| ▲ | agartner 5 hours ago | |
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. | ||
| ▲ | nulltrace 4 hours ago | parent | next [-] | |
Downtime is one thing. Silently reverting commits on your default branch is something else entirely. | ||
| ▲ | darknavi 4 hours ago | parent | prev | next [-] | |
Similar here. Somewhat ironic that a tool that was supposed to be preventing merge conflicts was authoring completely mangled commits to our mainline branch. | ||
| ▲ | robertwt7 3 hours ago | parent | prev [-] | |
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 | ||