# Could we use the new Stacked PR workflow?

**URL:** <https://discuss.python.org/t/could-we-use-the-new-stacked-pr-workflow/108383>\
**Category:** Core Development\
**Created:** [August 3, 2026, 1:14pm UTC](https://discuss.python.org/t/could-we-use-the-new-stacked-pr-workflow/108383 "2026-08-03T13:14:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jack1142](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/jack1142/32/2224_2.png) [@jack1142](https://discuss.python.org/u/jack1142)\
**Post date:** [August 3, 2026, 2:03pm UTC](https://discuss.python.org/t/could-we-use-the-new-stacked-pr-workflow/108383/2 "2026-08-03T14:03:19Z")

</div>

Something worth noting:

> Stacked pull requests require all branches to be in the same repository. Cross-fork stacks are not supported.

Which _I believe_ (but have not confirmed) means these would only work on upstream repo, if the branches of the PRs are also made on upstream repo.

> **[Where can you use stacked pull requests - About stacked pull requests - GitHub...](https://docs.github.com/en/pull-requests/get-started/about-stacked-prs#where-can-you-use-stacked-pull-requests)**
>
> Note | Break large code changes into a chain of smaller, dependent pull requests you can review and merge independently.

---

_[View the full topic](https://discuss.python.org/t/could-we-use-the-new-stacked-pr-workflow/108383)._