Repository navigation
github: Rebuild native stacks after merged prefixes - #1478
Merged
Merged
Conversation
Removing or reordering an open stack member can require unstacking and recreating native membership. Merged downstack PRs prevented that replacement because the compiler rejected any merged member and execution required an empty resource after unstacking. The active suffix stayed in its old stack with stale base branches. Allow replacement after a merged prefix by recording the historical merged PRs in the unstack instruction. Those PRs can remain in the old resource without preventing the released open PRs from being retargeted and stacked anew. Queued or auto-merge members still prevent replacement, and any other retained member stops dependent writes.
Owner
Author
|
This change is part of the following stack:
Change managed by git-spice. |
This was referenced Oct 24, 2026
This was referenced Oct 26, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removing or reordering an open stack member can require unstacking
and recreating native membership.
Merged downstack PRs prevented that replacement because the compiler
rejected any merged member and execution required an empty resource
after unstacking.
The active suffix stayed in its old stack with stale base branches.
Allow replacement after a merged prefix by recording the historical
merged PRs in the unstack instruction.
Those PRs can remain in the old resource without preventing the released
open PRs from being retargeted and stacked anew.
Queued or auto-merge members still prevent replacement,
and any other retained member stops dependent writes.