Repository navigation
ci: skip proposal creation when forced regeneration matches master - #28
Merged
Merged
Conversation
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.
A maintenance regression test reproduced the remaining forced-regeneration no-op case: when generated files already match master, the workflow still attempts to create a nonexistent or empty proposal. Skip the PR lookup/create phase only for that exact default-tree match. Preserve missing-PR recovery when a real proposal differs from master, and leave an existing identical proposal untouched. All nine regression tests now pass; the new test failed before this guard. No generated bindings, release metadata, or APIs change.