{{ message }}
fix(suite): retry reset push on non-fast-forward to unblock lifecycle#128
Merged
Conversation
Wrap cascade reset --state --push in a bounded fetch-and-retry loop so a concurrent write to main does not red the reset with a non-fast-forward rejection. Five attempts, growing backoff, fail closed on exhaustion. Matches cascade-example-4env#331. Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
Contributor
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
1 participant
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.
Wrap
cascade reset --state --push --config .github/manifest.yamlin a bounded fetch-and-retry loop so a concurrent write tomaindoes not red the reset with a non-fast-forward rejection. Five attempts, growing backoff, fail closed on exhaustion. Same fix as cascade-example-4env#331 (reviewer-approved), preserving this repo's--configflag and fail idiom; actionlint clean.