GitHub recently released a Stacked PRs feature that allows explicitly linking PRs into a stack of atomic but dependent changes. The most obvious way for Hoff to support working with these is probably to mirror how GitHub merges stacks natively, see this section. So for example, if I have a stack A -> B -> C, then issuing a merge command on B would first merge C, and then B. This would require enqueuing merges that do not have the default branch as their target, but instead the previous branch in a PR stack.
One open question with such an approach is whether to propagate a merge and deploy command. That is, in the previous example, would C also be merged as a deploy, or only B?
GitHub recently released a Stacked PRs feature that allows explicitly linking PRs into a stack of atomic but dependent changes. The most obvious way for Hoff to support working with these is probably to mirror how GitHub merges stacks natively, see this section. So for example, if I have a stack
A -> B -> C, then issuing amergecommand onBwould first mergeC, and thenB. This would require enqueuing merges that do not have the default branch as their target, but instead the previous branch in a PR stack.One open question with such an approach is whether to propagate a
merge and deploycommand. That is, in the previous example, wouldCalso be merged as a deploy, or onlyB?