GitHub Stacked PRs Simplify Code Reviews

GitHub just officially entered the stacked PRs game - and it's a big deal. 🎉 If you've never heard of stacked PRs, here's the idea: instead of one massive pull request that's painful to review, you break your changes into a chain of smaller, focused PRs that build on each other. Each layer is independently reviewable. CI runs on all of them. Branch protection rules apply across the whole stack. And when you're ready, you can merge the entire thing in one click. GitHub's new native implementation includes: - A visual stack map right in the PR UI - The gh stack CLI for managing branches, rebases, and pushes - Merge queue support that's stack-aware - Auto-rebase of remaining PRs after a merge No more rebase hell. No more wondering if CI is passing for mid-stack PRs. No more losing review context on a 2,000-line diff. The concept isn't new. Facebook built Phabricator around stacked diffs back in 2011. Tools like Graphite have offered this on GitHub for years. But having it natively supported changes things. The bottleneck in modern development is no longer writing code - it's reviewing it. Currently in private preview. Worth joining the waitlist if you work on large codebases or fast-moving teams. #GitHub #SoftwareEngineering #DevTools #CodeReview #DeveloperExperience

devpath-idp update — Phase 6. For those following along: I've been building an internal developer platform from the ground up and sharing the progress here. Phase 5 was software templates. Phase 6 is where things got interesting. One of the trickier debugging lessons I've had so far: A workflow completing successfully doesn't mean it actually did what you think it did. Here's what happened. Phase 6 is about the Backstage scaffolder — the part where a developer fills out a form and it automatically creates a GitHub repo, sets up the structure, and registers the service in the catalog. Self-service provisioning. That's the goal. I ran the template. The scaffolder showed steps completing. No obvious errors in the UI. It looked like it worked. Then I checked GitHub. The repo was empty. Something in the workflow had failed silently. The scaffolder didn't crash — it just didn't finish what it started. The GitHub push step timed out somewhere in the middle, and the UI wasn't loud about it. What made this tricky was the noise around it. When I restarted the backend during earlier sessions, the browser was throwing auth errors and stale token warnings. Those looked serious. They weren't — they were just the browser catching up after a restart. The real failure was quieter and further downstream. That's the thing about debugging distributed workflows: the loudest errors are often not the important ones. The important one here was silent — a repo that existed but had nothing in it. I'm still working through the fix. But the shift in understanding matters: I stopped asking "why is there an error?" and started asking "did this actually complete end to end?" Those are very different questions. And in platform engineering, the second one is usually the right one to ask first. Progress so far: ✅ Phase 1 — Base platform setup ✅ Phase 2 — GitOps foundation ✅ Phase 3 — Backstage portal setup ✅ Phase 4 — Catalog basics ✅ Phase 5 — Software templates 🔧 Phase 6 — Self-service provisioning (in progress) More on this when it's resolved. 🔧 #Backstage #PlatformEngineering #DevOps #InternalDeveloperPlatform #GitHub #Debugging #CloudEngineering #devpath

🚀 Day 93 of #1000DaysOfCoding Today was less about coding… and more about becoming a real developer. I finally moved my full-stack project from local to GitHub — sounds simple, but the journey was full of real-world challenges: 💥 Faced Git errors like large file limits 💥 Accidentally pushed node_modules (never again 😅) 💥 Learned why .gitignore is not optional 💥 Understood how Git actually tracks history (not just files) 💥 Fixed branch & remote issues like a pro And the best part? ✅ Clean repo structure ✅ Proper version control setup ✅ Ready for deployment 🚀 This wasn’t just “uploading code” — It was understanding how developers actually work in production. 💡 Small lesson: If your code works locally but you can’t version or deploy it — you’re not done yet. Next step: 👉 Deploying this project live (Frontend + Backend + DB) Let’s see how it goes 🔥 #1000DaysOfCoding #Day93 #Git #GitHub #FullStackDevelopment #SpringBoot #ReactJS #MongoDB #LearningInPublic #DeveloperJourney

If you've checked HackerNews or Lobsters this morning you'll see that GitHub has finally launched a stacked pull request in private preview. The long-awaited coding workflow is wait-list only at the moment, but that hasn't stopped devs and users from weighing in. The full story is on The Stack now. https://lnkd.in/e6m8qPP8

GitHub adds Stacked PRs to speed complex code reviews A new feature to facilitate code reviews and prepare for an AI-driven surge in code changes. My PoV included in InfoWorld news today. https://lnkd.in/gF9kzM42

Most Go developers are using GitHub Actions wrong — and it’s costing them speed, reliability, and clarity. I wrote this to break that pattern. The problem isn’t YAML. It’s the way we think about CI/CD. In this article, I walk through: – Why most pipelines become messy and fragile – The mindset shift from “scripts in YAML” → “clean orchestration” – How to structure Go workflows for speed, simplicity, and production reliability – What senior engineers do differently when designing CI Good CI isn’t about making builds pass. It’s about making systems trustworthy. If your pipeline feels slow, confusing, or brittle — this is for you. Read here: https://lnkd.in/dtYNh43T #golang #githubactions #devops #backend #softwareengineering #cicd

Stop picking libraries blindly. Start vibe checking them. Every developer has been burned by a dependency that looked great on paper: → 50k GitHub stars → Slick README → "Used by thousands of companies" Then 6 months later: ❌ Last commit: 8 months ago ❌ 400+ open issues, 3 maintainers left ❌ Breaking changes with no migration guide ❌ Bus factor: 1 Stars don't tell you if a project is alive. Downloads don't tell you if it's healthy. That's why I built Vibe Check — a free tool that gives every GitHub repo a social profile with real signals: 🏥 Health Score — 6 metrics (activity, community, bus factor, issue health, docs quality, commit velocity) rolled into a letter grade from A+ to F 📡 Live Signals — recent GitHub events, npm/PyPI download trends, Hacker News mentions — all in real time 🎁 Repo Wrapped — Spotify Wrapped but for repos. Commits this year, longest streak, top contributor, busiest day 🔍 Dependency Scanner — paste your package.json or requirements.txt, get a vibe check on every dependency at once. Find the weak links before they break your build. 📊 Trending Leaderboard — GitHub Trending repos ranked by vibe score, not just stars How it works: Go to bubbling.dev/vibe Paste any GitHub URL Get the full picture in seconds No login. No paywall. Just signal. The next time someone asks "should we use this repo?" — don't guess. Vibe check it. 🔗 bubbling.dev/vibe What library burned you the hardest? Drop it in the comments and I'll vibe check it live. 👇 #OpenSource #GitHub #DeveloperTools #SoftwareEngineering #TechDebt #Dependencies #WebDevelopment #DevTools

Elevating Code Review: GitHub’s Breakthrough in Diff Rendering Performance At AllSafeUs Research Labs, we constantly monitor advancements in developer tooling, recognizing their profound impact on security, productivity, and overall software quality. A recent announcement from GitHub, titled "The uphill climb of making diff lines performant," caught our attention, highlighting a crucial area often overlooked: the fundamental performance of code review tools. This initiative underscores a significant step towards optimizing the developer experience by tackling the intrinsic complexities of rendering code differences (diffs)....

You assign a GitHub issue before lunch. By the time you're back — there's a pull request waiting. That's the GitHub Copilot Coding Agent. GitHub Copilot has evolved far beyond autocomplete. The Coding Agent now works asynchronously in the background — fixing bugs, writing tests, refactoring code — and hands you a ready-to-review PR when it's done. Here's what just shipped: 🎛️ Model picker — Choose Claude Opus, Claude Sonnet, GPT-Codex-Max, or let Auto decide. Pick the right model for the complexity of each task. 🔍 Self-review — The agent reviews its own diff before tagging you. By the time you're looking at it, someone already went through it once. 🔒 Built-in security — Code scanning, secret scanning & dependency vulnerability checks — all before the PR opens. Free with Copilot coding agent. 🔌 MCP servers — Plug in external tools, databases, and context via Model Context Protocol. Your agent now has eyes beyond the repo. The agent boots a VM, clones your repo, RAG-indexes your codebase, and starts coding. You track every step in session logs. Your branch protections, CI/CD approvals, and security posture? Untouched. Think of it as having a junior dev who never sleeps, never skips tests, and always opens a clean PR. What low-to-medium complexity tasks would you hand off to an agent first? Drop a comment 👇 #GitHubCopilot #AI #CodingAgent #SoftwareEngineering #DevTools #AgenticAI #GitHub

I ran 12 coding agents on GitHub Issues simultaneously last month. Three fought over the same file, two got stuck in retry loops, and one burned through $40 before I noticed. The agent wasn't the problem. Everything around it was: workspace isolation, state tracking, failure recovery, cost controls. I was spending more time babysitting agents than writing the code myself. So I built Sortie, an open-source Go orchestrator that watches your issue tracker and dispatches coding agents to tickets. You write a config file, point it at GitHub Issues or Jira, pick your agent, and it handles the rest. Single binary, SQLite persistence. No Postgres, no Redis, no message queue. Kill the process, reboot, come back tomorrow. Every in-flight session and pending retry is still there. Tracker and agent adapters are pluggable: Jira, GitHub Issues, and Claude Code ship today. Swap one, everything else stays the same. 13 releases in 13 days, 41 docs pages, and the GitHub Issues adapter shipped today with v1.1.0. I wrote up the full story in a blog post. Links in the first comment. How are you running coding agents in production? #OpenSource #CodingAgents #GoLang #DevTools