Suggested test: copilot/threat-detection-report-as-issue-opt-out #16263

Motivation

github/gh-aw#61428 — "Allow opting out of '[aw] Detection Runs' tracking issue independently of threat detection". New safe-outputs.threat-detection.report-as-issue: false config skips creating/updating the [aw] Detection Runs tracking issue and posting comments to it, while keeping detection and enforcement (continue-on-error, safe-output blocking) active.

Proposed test

• Workflow file: test-copilot-threat-detection-report-as-issue-false.md
• Trigger: workflow_dispatch
• Engine: copilot
• Safe output: create-issue (as the primary output under test) plus threat-detection: { report-as-issue: false }
• Variant: standard

Minimal test prompt sketch

A workflow that enables threat-detection with report-as-issue: false and a benign create-issue safe output. The agent creates an issue as normal; the assertion is that no [aw] Detection Runs tracking issue/comment is created for this run, while the primary create-issue output still succeeds.

New fixtures or secrets needed

None, assuming the harness can check for absence of a [aw] Detection Runs issue update tied to the run ID. This may need a small e2e.sh assertion helper if one doesn't already exist for tracking-issue behavior.

Notes

No open suggestion or existing test currently covers threat-detection config at all (only copilot/custom-engine-threat-detection is open, #14834, which is about a different aspect — custom engine detection, not the report-as-issue opt-out). Filing as an issue since verifying "absence of a side effect" (no tracking issue update) may need harness support not yet confirmed to exist.

Generated by 🔍 Suggest New E2E Tests · copilot · auto · 70.4 AIC · ⌖ 9.19 AIC · ⊞ 8.4K · ◷