Optimize duplicate-code-detector workflow with precomputed analysis and tighter run scope#3997
Conversation
✅ Coverage Check PassedOverall Coverage
📁 Per-file Coverage Changes (1 files)
Coverage comparison generated by |
Smoke Test: Claude Engine
Result: PASS
|
🔬 Smoke Test Results
Overall: PASS PR by
|
🔥 Smoke Test: Copilot BYOK (Offline) Mode
Running in BYOK offline mode ( PR by Overall: PASS
|
|
Smoke Test Results: FAIL. Connectivity and MCP tool issues detected. Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "localhost"See Network Configuration for more information.
|
🏗️ Build Test Suite Results
Overall: 8/8 ecosystems passed — ✅ PASS
|
Smoke Test Results — FAIL ❌
Overall: FAIL —
|
duplicate-code-detectorwas spending most turns on deterministic discovery work (metrics/jscpd/grep), driving high token accumulation and long runtime. This change shifts that work into pre-agent workflow steps and narrows agent scope to prioritization + issue filing.Workflow execution model
stepsin.github/workflows/duplicate-code-detector.mdto run:jscpdinstallsrcandcontainers/tmp/gh-aw/*for agent consumption.Prompt reduction + scope constraints
Network + issue-surface tightening
network.allowedfrom["node","github"]to["github"].max: 3for lower issue churn per run.Compiled workflow + regression guard
.github/workflows/duplicate-code-detector.lock.ymlfrom updated source.scripts/ci/duplicate-code-detector-workflow.test.tsto assert: