You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Merge a stack that sits on another stack without dismissing approvals
#597
We chain stacks on each other (stack B's bottom PR is based on stack A's top branch). When stack A squash-merges into a squash-only main, B's bottom PR is retargeted and its merge base changes, so a "dismiss stale approvals" ruleset dismisses its approval and the merge stops there, even though its patch is unchanged. gh stack link refuses PRs that already belong to another stack, so the stacks can't be merged as one. It would help if gh stack merge could take several chained stacks in one atomic run, or if link could append one stack onto another.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
We chain stacks on each other (stack B's bottom PR is based on stack A's top branch). When stack A squash-merges into a squash-only main, B's bottom PR is retargeted and its merge base changes, so a "dismiss stale approvals" ruleset dismisses its approval and the merge stops there, even though its patch is unchanged.
gh stack linkrefuses PRs that already belong to another stack, so the stacks can't be merged as one. It would help ifgh stack mergecould take several chained stacks in one atomic run, or iflinkcould append one stack onto another.All reactions