ci: add optional ipfs_hash input to staker test reusable workflows - #4
Merged
Conversation
Adds a new optional 'ipfs_hash' input to staking-sync-test and staking-attestation-test. When the wrapper passes a pre-built IPFS hash (via repository_dispatch client_payload or workflow_dispatch input), the test job prefers it over the freshly built hash from the build job. When no input is provided, behavior is unchanged: the build job still runs and its hash is used. The build job is intentionally kept always-on for now; this is purely forward-looking plumbing so the wrappers can forward the dispatch payload's ipfs_hash. A future change can short-circuit the build job when an input hash is present.
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.
Adds an optional
ipfs_hashinput tostaking-sync-test.ymlandstaking-attestation-test.yml.Behavior
repository_dispatchclient_payload orworkflow_dispatchinput) → the test job prefers it over the freshly built hash.Why
Wrappers in the 10 staker package repos are about to forward an
ipfs_hashfrom TropiBot's dispatch payload. The reusable workflows need to accept that input. The build job is kept always-on for now; a follow-up can short-circuit it when an input hash is present.