--- title: Medium | daily.dev description: A team struggling to organize a multi-part authentication feature (database, API, frontend, tests) across dependent pull requests discovered GitHub Stacks, a... canonical: https://daily.dev/posts/medium-rnwumm3b3 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Medium | daily.dev og:description: A team struggling to organize a multi-part authentication feature (database, API, frontend, tests) across dependent pull requests discovered GitHub Stacks, a... og:url: https://daily.dev/posts/medium-rnwumm3b3 og:image: https://api.daily.dev/og/posts/rNWUMm3b3.png og:image:alt: Medium og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Medium **[Medium](https://daily.dev/sources/medium_js)** · 2 min read · 1 upvotes · 0 comments ## Summary A team struggling to organize a multi-part authentication feature (database, API, frontend, tests) across dependent pull requests discovered GitHub Stacks, a feature that lets PRs be built on top of each other while preserving their dependency relationships. Instead of one giant PR or a tangle of disconnected branches, stacks allow reviewers to go through smaller, ordered PRs (database, then API, then frontend, then tests), and changes to an earlier PR propagate cleanly through the stack. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is GitHub Stacks and how does it help with dependent pull requests? GitHub Stacks lets developers build a series of smaller pull requests on top of each other instead of one large PR or disconnected branches. For a feature spanning database migrations, API changes, frontend changes, and tests, each part becomes its own PR stacked in dependency order, so reviewers can review the database changes first, then the API on top, then frontend and tests, while changes to an earlier PR stay connected to the ones built on top of it. _Teams debating how to split dependent PRs can find workflow write-ups like this through daily.dev._ ## Similar posts on daily.dev - [GitHub adds Stacked PRs to speed complex code reviews](https://daily.dev/posts/github-adds-stacked-prs-to-speed-complex-code-reviews-ufanab95z) · InfoWorld · 0 upvotes · 0 comments - [GitHub invokes spirit of Phabricator with preview of Stacked PRs](https://daily.dev/posts/github-invokes-spirit-of-phabricator-with-preview-of-stacked-prs-ybrvrjtnz) · DEVCLASS · 3 upvotes · 0 comments - [GitHub Stacked PRs](https://daily.dev/posts/github-stacked-prs-ekt9rnyqu) · Hacker News · 2 upvotes · 0 comments --- Tags: [#github](https://daily.dev/tags/github), [#git](https://daily.dev/tags/git), [#code-review](https://daily.dev/tags/code-review) [View this post on daily.dev](https://daily.dev/posts/medium-rnwumm3b3) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Medium","url":"https://daily.dev/posts/medium-rnwumm3b3","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/medium-rnwumm3b3"},"datePublished":"2026-08-16T13:58:36.555Z","dateModified":"2026-09-13T19:56:46.683Z","description":"A team struggling to organize a multi-part authentication feature (database, API, frontend, tests) across dependent pull requests discovered GitHub Stacks, a...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d6ab0a9a223ee01bc82d647f54feb2d2?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d6ab0a9a223ee01bc82d647f54feb2d2?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Medium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Medium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/medium","url":"https://daily.dev/sources/medium_js"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/medium-rnwumm3b3","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"github,git,code-review","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Medium","item":"https://daily.dev/sources/medium_js"},{"@type":"ListItem","position":3,"name":"Medium"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/medium-rnwumm3b3#faq","mainEntity":[{"@type":"Question","name":"What is GitHub Stacks and how does it help with dependent pull requests?","acceptedAnswer":{"@type":"Answer","text":"GitHub Stacks lets developers build a series of smaller pull requests on top of each other instead of one large PR or disconnected branches. For a feature spanning database migrations, API changes, frontend changes, and tests, each part becomes its own PR stacked in dependency order, so reviewers can review the database changes first, then the API on top, then frontend and tests, while changes to an earlier PR stay connected to the ones built on top of it. Teams debating how to split dependent PRs can find workflow write-ups like this through daily.dev."}}]} ```