Migrate from GitHub to GitLab for Reliability

Easter Sunday is not the time to find out your deploy pipeline is still open. We've all seen it. A PR gets merged late Friday "just to get it in." By Sunday someone's getting paged. The on-call engineer is not happy. NoShip lets you set a recurring freeze that kicks in automatically every holiday weekend. Define the window once, and GitHub enforces it. No Slack reminders. No honor system. No "I thought someone else handled it." Set it. Forget it. Enjoy the long weekend. #DevOps #GitHub #CodeFreeze #SRE #PlatformEngineering #DeploymentSafety #Easter

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

Everyone jokes about rm -rf *… until it actually happens. A while back, GitHub engineer accidentally accidentally ran a destructive command on the wrong repository. Not a fork. Not a personal project. The company’s main GitHub repo. Within seconds… pipelines failed. Services broke. Data disappeared. Panic kicked in. And this wasn’t a small startup. This was at the scale where even minutes of downtime matter. But here’s the part no one talks about 👇 The system came back. Why? Because great engineering isn’t about never making mistakes. It’s about designing systems that survive mistakes. -> GitHub backups saved them -> Branch protections prevented even worse disasters -> Teams jumped in and fixed things fast Within hours, everything was restored. 💡 The lesson? If you’ve ever broken something in code, accidentally deleted a branch, or messed up production… You’re not alone. Even the best engineers have done it. The difference isn’t perfection. The difference is how fast you recover and what you learn. So next time you make a mistake… Don’t panic. Improve your system. Because in tech, mistakes are not the end. They’re part of the process. #github #programming #softwareengineering #devlife #learning #growth #tech

It's Friday afternoon. Someone just opened a PR. Your freeze policy says no merges after 3pm Friday. But it's not enforced anywhere. It's just a rule people vaguely know about. So the PR sits there, and someone with merge access makes a judgment call. This is how most "no Friday deploys" policies actually work: tribal knowledge, good intentions, and crossed fingers. Works fine until it doesn't. NoShip turns that policy into a required status check on GitHub. No merges get through during a freeze, full stop. No judgment calls required. You can even ask it in Slack: "freeze all repos every Friday at 3pm for 48 hours" and it'll set the recurring schedule. Done. Have a good weekend. #DevOps #GitHub #CodeFreeze #SRE #PlatformEngineering #DeploymentSafety #EngineeringLeadership

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 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's update on availability is a compelling read. They're scaling for an incredible 30x growth by 2026, primarily driven by the explosion of "agentic development workflows." This really highlights how AI-driven dev is already pushing infrastructure to its limits. Good to hear their detailed plans for reliability and transparency after recent incidents. 🚀 #GitHub #AIDev

Oof, March was a rough one for GitHub. Multiple incidents, including Copilot and Actions downtime, really makes you appreciate reliability. Glad they're implementing killswitches and dedicated hosts. #GitHub #DevOps

Easter weekend is when "please don't merge anything" gets tested. Someone ships a "small fix" Friday afternoon. The on-call phone rings Saturday morning. Half the team is debugging instead of doing whatever they planned. The manual freeze: send a Slack message, hope everyone sees it, remind the one person who didn't, and still watch a PR slip through because branch protection doesn't care about your message. NoShip turns "please don't merge" into an actual rule. Set a recurring freeze for holiday weekends and GitHub enforces it. PRs block automatically. No honor system required. If something genuinely needs to go out anyway, the dual-approval override workflow means two people sign off before a single PR gets through. Full audit trail captures who approved it and why. Enjoy the long weekend. #DevOps #GitHub #CodeFreeze #SRE #EngineeringLeadership #Easter #DeploymentSafety

The GitHub outage two days ago blocked what I was doing pretty badly. Yes, I could have worked on something else, but stopping my flowstate was an extremely disruptive endeavor, and I nearly considered just going home early. Is it time that we think about abandoning ship and moving to other source control solutions? GitHub instability has been really bad lately, and I don't see any reason why it will get better.