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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This workflow now triggers on any completed
Testrun onmain, butTestalso runs forpull_requestevents (.github/workflows/test.yaml), andworkflow_runjobs can access privileged secrets/tokens; without checkinggithub.event.workflow_run.event == 'push', a successful PR-originated test run can enter this deploy path and publish/tag code outside the intended post-merge release flow. Add an explicit event guard (and optionally same-repo guard) so only main-branch push test runs can deploy.Useful? React with 👍 / 👎.