abadideahey "haha github uptime lol" and all that but this is serious: some pull request merges were completely mangled yesterday and the repo may not be in the state that its maintainers expect. If your project processed any updates yesterday, please double-check https://www.githubstatus.com/incidents/zsg1lk7w13cf
this is secondary but I don’t love how they completely changed the “Resolved” description within the last hour while leaving the timestamp at 13 hours ago
Lynn@0xabad1dea That's a yikes for sure
Astrid@0xabad1dea They have to pretend it was resolved quickly 🙃
@luxliquida to be clear, it already said it was resolved since yesterday. What changed is the textual description of the resolution event, without being indicated.
(the change was roughly from "We will provide instructions on how to mitigate as soon as possible" to "those affected have been contacted". this isn't some shocking coverup, just bad practice to overwrite and keep the old timestamp)
@0xabad1dea Oh, I figured as much. But I doubt it's an isolated bad practice, and it speaks to a larger culture of "make sure the dates are good for PR"
Stylus@0xabad1dea @luxliquida anybody have an example of a wrong merge in the wild"? I wonder if it's subtly wrong or blindingly wrong...