Disable threat-detection phase in copilot-token-optimizer#27426
Merged
Disable threat-detection phase in copilot-token-optimizer#27426
copilot-token-optimizer#27426Conversation
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/aea4f5d5-1b6d-40bc-9e0b-8838c5bb5420 Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
lpcox
April 20, 2026 20:51
View session
Collaborator
|
@copilot merge main and recompile |
Contributor
There was a problem hiding this comment.
Pull request overview
Disables the generated threat-detection phase for the copilot-token-optimizer agentic workflow so the workflow no longer depends on (or blocks on) the compiled detection job.
Changes:
- Updated workflow frontmatter to set
safe-outputs.threat-detection: false. - Regenerated the compiled lock workflow to remove the
detectionjob and all downstreamneeds/output wiring.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/copilot-token-optimizer.md |
Adds threat-detection: false under safe-outputs to disable threat detection for this workflow. |
.github/workflows/copilot-token-optimizer.lock.yml |
Regenerated compiled workflow: removes detection job and associated dependencies/output references. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
Author
Merged 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:
If you need me to access, download, or install something from one of these locations, you can either:
|
Contributor
|
Nice fix from the Copilot coding agent — disabling the One mechanical flag: no test changes detected. For a workflow YAML config change like this, unit tests are genuinely not applicable — there's no Go logic to exercise. That said, if the project has a If you'd like to add a lightweight validation step: Overall this is well-scoped and follows the core team process correctly. 🟢
|
This was referenced Apr 20, 2026
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.
Copilot Token Usage Optimizerwas failing due to the generated threat-detection phase (detectionjob) in its compiled workflow. This change disables threat detection for this workflow so runs no longer depend on that phase.Workflow config change
.github/workflows/copilot-token-optimizer.mdto explicitly disable threat detection in safe outputs.Compiled workflow impact
.github/workflows/copilot-token-optimizer.lock.yml.detectionjob and relatedneeds/detection output wiring from downstream jobs.Resulting behavior