GitHub Merge Queue Issue Causes Incorrect Commits

Even the giants have "off" days: Lessons from GitHub’s Merge Queue regression. GitHub recently confirmed a bug where roughly 2,800 pull requests were merged from the wrong base state, unintentionally reverting previous changes. While 0.07% sounds small, in production, "small" percentages can mean major downtime. Key Takeaways for Teams: 1)Automated Testing is King: GitHub is already expanding test coverage for merge operations. 2)Trust, but Verify: Always keep an eye on your branch history after a merge, especially when using automated queues. 3)Transparency Wins: Kudos to Kyle Daigle and the GitHub team for the quick RCA (Root Cause Analysis) and direct outreach to affected users. Have you ever encountered a "silent revert" in your workflow? How does your team guard against tool-level regressions? #GitHub #DevOps #SoftwareEngineering #CI/CD #TechNews

Most coverage tools give you the wrong number. They'll happily report that your codebase is 90% covered, while the 200 lines you just merged have zero tests. Looks great on a dashboard. Doesn't help anyone in review So I built a GitHub Actions that only reports coverage + lint quality on the lines your PR changed. Just the new code and new violations but my favorite feature is that it annotates code that isn't covered. A few weeks later it's live on the GitHub Marketplace, running across our internal repos, and starting to show up in other teams' CI pipelines too If your team ships PRs and mostly wants to know how much the new code is tested, link's in the first comment. #OpenSource #DeveloperExperience #SoftwareEngineering #GitHubActions #DevOps

GitHub's merge queue silently rewrote main branch history on April 23rd. The pattern: PR shows a +29 / -34 diff. Reviewed, approved, queued. What lands is +245 / -1,137 — thousands of lines of already-shipped code quietly removed. Every merge after that stacks on the broken history. UI shows nothing wrong. GitHub says 2,800 PRs out of 4 million. One company reported 200+ on its own. Pick a number. The part nobody's saying out loud: for history to get overwritten like this, something is force-pushing to main behind the scenes. Branch protection apparently doesn't apply to GitHub itself. Worth thinking about what else moves through that path silently. The deeper issue isn't the bug. Bugs happen. The issue is that "distributed version control" became a single vendor's merge button for most of the industry, and the merge button lied for a day. Git itself was fine the whole time. It always is. I run my own Gitea. Recommend it. #GitHub #Git #DevOps #Gitea #SelfHosted #SoftwareEngineering

GitHub Branch Protection: Advanced Rules for Status Check Dependencies Master advanced branch protection configurations that go beyond basic reviews. Learn to set up dependent status checks, automatic review dismissal, and linear history enforcement for enterprise-grade code quality control. Read the full how-to guide: https://lnkd.in/gB3fSePc #ITTips #Productivity #DevOps #GitHub #TechTips #OpenSource #SoftwareDevelopment #BranchProtection #CodeQuality #GitWorkflow

🚨 Issues with #GitHub today? We’re seeing instability across the platform: ❌ Push & pull delays ❌ Pull Requests not loading ❌ Actions (CI/CD) failing or stuck ❌ Overall slow performance This is not a local issue — it’s affecting multiple environments. 💡 What I did (and what I recommend): I moved to running my own Git server using Gitea Open Source — and honestly, this is something more teams should consider. https://git.xdeye.com/ 👉 Here’s the practical advice: ✔️ Keep a self-hosted Git backup (Gitea / GitLab / bare repo). ✔️ Push your code to multiple remotes (GitHub + your own server). ✔️ Don’t depend fully on GitHub Actions — have manual or server-based deployment ready. ✔️ Keep production deployment independent from third-party outages. ✔️ Automate locally or on your own server where possible. Now my workflow is: Local → self-hosted Git → live servers GitHub is secondary, not critical ⚠️ With the growing use of AI tools and third-party automation inside CI/CD pipelines, complexity and risk are increasing. When one piece fails, everything can break. Better to stay in control. How are you handling redundancy in your Git workflow? #GitHub #DevOps #SelfHosted #Gitea #CI #CD #Security #ITInfrastructure

"I want to code. And I can't code with GitHub anymore." That's Mitchell Hashimoto. GitHub user #1299. The man who built Terraform and Vagrant. After 18 years — he's moving Ghostty off GitHub. And I don't blame him. For a month he kept a journal. Every day GitHub disrupted his work, he marked an X. Almost every day had one. Then April 23: a squash merge bug corrupted 658 repos and 2,092 PRs. That's not downtime. That's data loss. Then April 27: All of GitHub — search, Issues, PRs, Projects — went completely dark. GitHub's CTO apologized. Said they now need 30× capacity. February alone had 37 platform incidents. Here's what nobody's saying: GitHub is bending under the weight of agentic AI. Copilot sessions. Parallel agents. Millions of automated calls per minute. The platform was never designed for this. And it's cracking. When the person who defined modern DevOps infrastructure says GitHub is "no longer for serious work" — that's not a hot take. That's a warning. Where do you go when GitHub goes down? 👇 #GitHub #OpenSource #Ghostty #Developers #DevTools #SoftwareEngineering #Tech #BuildInPublic

Hard freeze: the system won't let you merge. Soft freeze: "please don't merge." Guess which one works. Every "Slack-message-and-hope" freeze I've seen eventually gets violated. Sometimes by a well-meaning engineer who missed the thread. Sometimes by a contractor who isn't even in the channel. Sometimes by the merge queue itself, which doesn't read Slack at all. The fix isn't better communication. It's a required status check that says no. NoShip turns your freeze into a GitHub check that blocks merges at the source — across every repo, every branch, every environment. Policy becomes control. No honor system required. #CodeFreeze #DevOps #GitHub #SRE #PlatformEngineering #DeploymentSafety #EngineeringLeadership #ChangeControl

So GitHub now lets orgs disable commit comments. I can already hear the collective sigh of relief from maintainers drowning in long-dead discussions on ancient lines of code. Or maybe a collective groan from those who loved the context? Either way, a powerful new admin lever. What's your take on this cleanup? #GitHub #DevOps

GitHub's latest update is a welcome relief for notification fatigue! They're tweaking notification retention periods and, even better, archived repository watches won't be sending you alerts anymore. Finally, some peace for those old, dusty projects! 🙌 A small change, but it really helps keep the focus on what matters. #GitHub #DevOps

50 reruns for GitHub Actions workflows feels a bit tight, doesn't it? Makes you really think about why a workflow failed in the first place. Time to get serious about debugging! #DevOps #CI/CD