Repository navigation
upstreaming: register safe fork CI and forbid unrelated debug changes - #4961
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.
Summary
push: riscv64when an existingpull_requesttrigger covers the development PR base;inputs.upload, addgithub.event_name == 'push', or alter unrelated event, artifact-retention or release behavior for fork validation;Live evidence
Development PR #1 has the correct riscv64 matrix changes, but its debug commit also added an unnecessary push trigger and broadened artifact upload behavior. The base workflow already has
pull_requestformaster, so these changes are unrelated and must be removed.No CI ran because the fresh fork has three workflow files but its Actions API inventory is empty. A prior enable-by-filename attempt returned 404 because workflows were not registered. The existing marked PR operation remains retriable; after registration and safe enablement, the workflow reopens that exact PR once to emit the standard event.
Validation