Repository navigation
Comparison: two plunge updates apply side by side once the first has landed - #22
Merged
Merged
Conversation
…landed A direct run on floci (plywood#55, 2026-11-02): the second merge carries the first's change, so at the same moment one is refused and re-run. Co-Authored-By: Claude Opus 5.5 <[email protected]>
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.
Corrects plywood's cell in the plunge row "Two updates to one stack, on different resources, run side by side", per plywood#55's direct run on 2026-11-02. The second merge's commit carries the first merge's change, so while the first still applies, plunge's per-resource record saves one of them and the other is refused and re-run. The cell goes from good to warn.
Co-Authored-By: Claude Opus 5.5 [email protected]