Rendered at 16:19:42 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
cwkcw 5 days ago [-]
The window to audit is 2026-04-23 16:05 to 20:43 UTC, about 4h 38m, and 'merged incorrectly' is unpacked in exactly no detail on the status page. Practical check is to compare the tree of each merge commit in that window against the tree of the rebased-and-tested commit that the queue ran CI on. GitHub Enterprise Cloud with Data Residency is still affected as of the latest status update, so DR customers shouldn't clear new queue merges yet. Would be kinda useful if GitHub published the specific failure mode, because content-drift and parent-linkage and dropped-changes all need different audit scripts.
matthewbauer 5 days ago [-]
Might want to check your git logs if you are using the Merge Queue feature. This afternoon, we found that Merge Queue was silently reverting changesets in the merge queue. Acknowledged by GitHub, but could be a very hard problem to debug if you aren't looking for it.
EdwardDiego 5 days ago [-]
Same here, ffs GH.
MarkMarine 4 days ago [-]
4 people spent hours putting our repo back together at my company after this. GH has been unreliable and now they are breaking the core tenant of what I expect from this service.
I don't care to associate with people who are offended by being corrected. They can sod off. And I never go to what you Americans call "parties".
ThePrimeagen 1 days ago [-]
> And I never go to what you Americans call "parties".
Whenever you use quotes and they are directly followed by punctuation you must include the punctuation within the quotes.
"parties."
ragall 20 hours ago [-]
That's the American style, and it's stupid.
ilyasok 3 hours ago [-]
It's English, my fair cross-dressing sweaty nerd. Go read a book for once in your lifetime. Harry Potter at the very least.
“The best,” replied Severus Snape.
-- Harry Potter And The Deathly Hallows, p.1
dariusve 2 hours ago [-]
I recommend this book: Rebel with a Clause: Tales and Tips from a Roving Grammarian by Ellen Jovin
MarkMarine 2 days ago [-]
This type of pedantry doesn’t add to the discussion. You’re correcting someone’s spelling on the internet, it’s pointless except to make you feel superior, adds nothing. Make a salient point, bring something to the discussion please. Sorry I hurt your feelings bud.
ptdorf 13 minutes ago [-]
You guys are all ugly and you smell.
chylex 3 hours ago [-]
Yes it does. The original commenter can learn how to spell better which makes clear communication easier, and don't forget that other people read internet discussions and they may be learning new words or realizing they also didn't know how to spell a word correctly. You seem offended at the prospect of people learning how to do something correctly, I don't get it.
ragall 20 hours ago [-]
You didn't hurt my feelings, buddy. And if you don't understand what I did and why... pity.
mazeez 4 days ago [-]
[flagged]
acid__ 5 days ago [-]
Tip: identify PRs with this problem by looking for discrepancies between the metadata (files/lines affected) for PRs via GitHub API and associated commits in the time window.
This was a pain to clean up!
EdwardDiego 5 days ago [-]
This has caused a morning of fun for our team, how do you break one of the most fundamental bits of your system? Time to look at alternatives...
ramon156 4 days ago [-]
Self-hosting has been wonders. I thought I needed the social part of GH (i still kind of do, I like seeing what people are working on or liking) but overall its the same experience.
NelsonMinar 4 days ago [-]
How did a bug like this get past their testing?
philpem 4 days ago [-]
Given the push to AI/Copilot from MS I'd be impressed if they still did any testing.
estimator7292 4 days ago [-]
They're at 88% uptime this year. I don't think they have testing.
tracker1 4 days ago [-]
Microslop®, unmatched quality.
tracker1 4 days ago [-]
I experienced a weird bug, where the github ci environment was checking out code that was throwing an error on build... the version tag definitely didn't have the code the error was coming from... I messed with the CI workflow yaml and finally cat'd the file in question... the error code was definitely there (2 lines repeated in the file) that was not in the repository.
I nuked the release tag and re-created it, and it started working... was just a really weird bug/experience.
sidewndr46 4 days ago [-]
Github has been doing this for at least 5 years now. Merging a pull request merges whatever the latest commit on that branch is in the specific backend that handles the merge request. It does not merge what was just pushed into that branch.
orpheansodality 5 days ago [-]
for other folks currently in an incident trying to resolve the chaos this caused, the first commit we've found with issues in our repo is from ~10:30am pacific this morning
5 days ago [-]
classified 4 days ago [-]
How long will users put up with this before they finally leave? Microslop is inventing new failure modes on a weekly basis.
jonnonz 3 days ago [-]
Whats going on over there, is clippy in charge of the release button?
tenet not tenant
"parties."
“The best,” replied Severus Snape. -- Harry Potter And The Deathly Hallows, p.1
This was a pain to clean up!
I nuked the release tag and re-created it, and it started working... was just a really weird bug/experience.