GitHub’s new Stacked Pull Requests feature restructures how developers submit and review changes by allowing large code updates to be broken into smaller, interdependent units. With Stacked PRs, each unit can be reviewed and merged individually while still contributing to the overall feature set. The approach helps developers shift away from monolithic pull requests, which have become increasingly difficult to manage as development continues to move faster. The release of Stacked PRs is a response to the rise of AI-assisted coding tools, which have greatly increased the volume and scale of code submissions, placing new pressure on review workflows. While large pull requests spanning dozens of files used to be merely inconvenient, they are sometimes now a systemic issue. There is a widening gap between code generation and code review, with reviewers dealing with reduced visibility and slower turnaround times. With the layered workflow of Stacked PRs, developers can sequence related...
If you work in DevOps, you’ve probably had this experience: You ship something. It works. Performance looks good. Deployment is clean. A few weeks later, someone from finance shows up asking why costs spiked 30%. Now you’re digging through logs, trying to reconstruct decisions you made weeks ago, in a completely different context. That’s not a FinOps problem. That’s a workflow problem. The Real Issue: Cost Lives Outside the Pipeline Most DevOps teams have spent years tightening feedback loops: Code quality → caught in PRs Security → caught in CI Performance → caught in testing Cost is the outlier. It typically shows up: After deployment In a separate dashboard Owned by a different team Which means it’s not actionable when it matters. You can’t fix what you can’t see *in context*. Why DevOps Teams End Up Owning Cloud Cost Anyway ...