GitHub lets orgs disable commit comments

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

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 rolling out some neat updates to its standard code findings. Less noise, more signal when scanning those public repos. Definitely worth a look if you're building in the open. #CodeQuality #DevTools

GitHub had a clever "chicken and egg" problem: needing GitHub to deploy GitHub! 🐔🥚 They're solving tricky circular dependencies in deployments by using eBPF to selectively block problematic network calls. What's even cooler? They can trace those blocked requests back to the specific command. Super smart for safer deployments and faster incident recovery! #eBPF #DevOps

𝗠𝗮𝗻𝗮𝗴𝗶𝗻𝗴 𝗺𝘂𝗹𝘁𝗶𝗽𝗹𝗲 𝗚𝗶𝘁𝗛𝘂𝗯 𝗮𝗰𝗰𝗼𝘂𝗻𝘁𝘀 𝘀𝗵𝗼𝘂𝗹𝗱𝗻’𝘁 𝗯𝗲 𝘁𝗵𝗶𝘀 𝗽𝗮𝗶𝗻𝗳𝘂𝗹… 𝗯𝘂𝘁 𝗶𝘁 𝗶𝘀. Over the past few months, I kept running into a frustrating issue: using work + personal GitHub accounts on the same machine without breaking SSH or mixing identities. So I built a clean, repeatable SSH setup that solves the following: • Authentication conflicts • Wrong-account commits • Broken push/pull workflows What’s inside the guide: • Separate SSH keys per account • Smart aliasing via ~/.ssh/config • Per-repo Git identity setup • Quick debugging checks The goal was simple: 👉 Make it predictable and production-safe—not just “works on my machine." If you’ve ever pushed code from the wrong account… you know the pain. 😅 🔗 GitHub repo: https://lnkd.in/dFH75WvV If this helps, consider giving the repo a ⭐ #github #git #ssh #developers #webdev #softwareengineering #opensource

GitHub just rolled out a Rule insights dashboard and a unified filter bar! This is great for anyone managing repos with complex rule sets. Finally, a clearer view on how those rules are performing and easier filtering. Little quality-of-life updates like these make a big difference in daily dev work. #GitHub #DevTools

GitHub engineers really tackled the performance issues in large pull requests. It's impressive how optimizing tiny things like reducing DOM nodes per line can make such a difference. Makes you appreciate the unsung heroes of front-end performance! #GitHub #Engineering

Critical Infra like Github having this kind of incidents would be unthinkable 3-4 yrs ago, Also their uptimes lately have not been that great. What changed? I also sympathise with them due to huge amount of code generated by Agents & AI being pushed on a scale couldn't be imagined before but even that shouldn't be an excuse for this kind of errors. Git & Github are too critical for these kind of goof ups.

🚨 Is GitHub's reliability hurting your team? I've been talking with many customers recently, and a common theme keeps coming up — frustration with GitHub's service health. Outages, degraded performance, and uncertainty around uptime are slowing teams down. If that sounds familiar, there's a path forward. In 3 days, I'll be running a free workshop walking through how to migrate from GitHub to GitLab — step by step, no guesswork. You'll leave with a clear migration plan, practical tips, and confidence to make the switch. 👉 Interested? Join us here: https://lnkd.in/d-ckV-9G Quinten Dismukes, Colin Stevenson, Thiago Magro, Adrian Tigert #GitLab #GitHub #DevOps #Migration #Workshop

I bet the next billion-dollar product is probably sitting in a private GitHub repo right now just a founder who keeps saying "it's not ready yet"