Heidelberg AI News

Video · GitHub ·

Stop waiting on your own pull requests: GitHub stacked PRs in practice

In short

GitHub stacked PRs split large, dependent changes into smaller pull requests that can be reviewed and merged incrementally. The workflow is designed for agentic development and monorepos, reducing review bottlenecks while preserving branch protection, CI, and commit history.

Key points

  • Stacked PRs are generally available on all github.com plans.
  • Repositories using stacked PRs merge 9% more code on average.
  • More than two-thirds of the top 1% of repositories use stacks, with 5% faster merge times.
  • The GitHub CLI `gh stack` handles stack creation, cascading rebases, and Git worktrees.
  • A stack can use parallel agent sessions, with each layer isolated in its own worktree.
  • All PRs in a stack inherit the target branch's CI workflows and branch protection rules.
  • Atomic merges, auto-merge, VS Code, and GitHub.com support let teams manage and merge stacks as a unit.

Written by an AI model from the video’s captions and description.

Big pull requests slow everyone down, creating review bottlenecks, stalling feedback loops, and disrupting developer momentum.

Watch on YouTube The opening of the article at youtube.com.

In this story

A tool or model opens in the Heidelberg AI Curriculum: what it does, what it costs, how to start. A repo opens on GitHub.

Related stories

All stories