Remove workflow_run trigger from test-safe-output-missing-tool workflow #816
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.
This PR removes the
workflow_runtrigger from the test workflow for missing tool safe outputs, simplifying the trigger configuration to only use manual execution.Changes Made
workflow_runtrigger: The workflow previously triggered on completion of any workflow (workflows: ["*"]withtypes: [completed]), which could cause unnecessary executionsworkflow_runtrigger from the workflow's documentation section.lock.ymlfile to reflect the trigger changesBefore
After
Rationale
The
workflow_runtrigger was causing the test workflow to execute after every workflow completion in the repository, which is unnecessary for a test workflow focused on validating missing tool safe output functionality. The workflow is now triggered only via manual execution (workflow_dispatch), making it more predictable and reducing unnecessary workflow runs.The test workflow's primary purpose is to validate the missing-tool safe output type functionality using a custom engine, and manual triggering is sufficient for this testing purpose.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
api.contoso.com/tmp/go-build2366863216/b278/cli.test -test.testlogfile=/tmp/go-build2366863216/b278/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true(dns block)/tmp/go-build2628927492/b278/cli.test -test.testlogfile=/tmp/go-build2628927492/b278/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.