26
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 31 Jul 2026
26 points (88.2% liked)
Programming
27973 readers
280 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
That is the point. By making smaller PRs, you inevitably end up with dependencies between them. So you'd like to stack them.
Maybe I just don't know enough how these work, as I've never heard of stacked prs before.
What does the workflow look like? Can the first PR be merged and deployed without the other prs being approved and merged first? Or do they all need to be approved and it all gets merged together?
I haven't used it yet but assuming they did it right, yes you can merge the PRs sequentially.
Assuming it's like gitlab's stacked PRs, all the merge requests are independent. It's basically "just" rebasing the stack once the bottom gets merged.