Overview
Update .github/workflows/windows-cli-integration.yml so its conclusion job creates a GitHub issue when the build or Windows integration job fails.
Key gap
The workflow already aggregates build and integration results, includes the failed job names and run link in the step summary, and fails the run. It does not create an issue as required. Grant only the conclusion job the minimum issue-write permission needed, and include the failed job names and current run URL in the issue.
Relevant workflow coverage
The existing workflow includes a daily schedule and manual dispatch, an Ubuntu cross-build with artifact upload, Windows integration runs across pwsh, Windows PowerShell, and cmd, a shell/launch/environment/path scenario matrix, explicit path and PATHEXT checks, unicode and minimal-environment cases, command help and unknown-command checks, timeouts, a ConPTY probe, and stdin hang detection. The missing behavior is failure-triggered issue creation from conclusion.
Next action
Add failure-only issue creation to conclusion, preserving its current aggregation and overall failure result. Make repeated scheduled failures manageable, for example by updating or reusing an open tracking issue where practical.
References:
Generated by 🪟 Daily Windows Terminal Integration Builder · codex · gpt60 · 48.3 AIC · ⌖ 27.1 AIC · ⊞ 15K · ◷
Overview
Update
.github/workflows/windows-cli-integration.ymlso itsconclusionjob creates a GitHub issue when the build or Windows integration job fails.Key gap
The workflow already aggregates
buildandintegrationresults, includes the failed job names and run link in the step summary, and fails the run. It does not create an issue as required. Grant only the conclusion job the minimum issue-write permission needed, and include the failed job names and current run URL in the issue.Relevant workflow coverage
The existing workflow includes a daily schedule and manual dispatch, an Ubuntu cross-build with artifact upload, Windows integration runs across
pwsh, Windows PowerShell, andcmd, a shell/launch/environment/path scenario matrix, explicit path andPATHEXTchecks, unicode and minimal-environment cases, command help and unknown-command checks, timeouts, a ConPTY probe, and stdin hang detection. The missing behavior is failure-triggered issue creation fromconclusion.Next action
Add failure-only issue creation to
conclusion, preserving its current aggregation and overall failure result. Make repeated scheduled failures manageable, for example by updating or reusing an open tracking issue where practical.References: