Stacked pull requests break large changes into small, reviewable pull requests. They’re an ordered series of pull requests that each represent focused layers of your change. With stacks, you can…
It seems like something we allready do at work, with feature-branches that collect multiple prs that are required for a feature, but with some proprietary bits and bops instead of an internal procedure and standard git features.
i guess it’s nice for people who use github in their team, but it furthers lock-in.
im not sure if I care tbh. seems gimmicky
It seems like something we allready do at work, with feature-branches that collect multiple prs that are required for a feature, but with some proprietary bits and bops instead of an internal procedure and standard git features.
i guess it’s nice for people who use github in their team, but it furthers lock-in.
agreed, happens in our org quite often as well previously just done via separate chained PRs and required rebasing after each merge
that describes everything github does these days