Repository navigation
[windows-integration] Create an issue when Windows CLI integration jobs fail #66016
Description
Overview
The Windows CLI integration workflow already builds the Windows binary, runs a broad set of shell and environment checks, enforces timeouts, and aggregates job outcomes. Its conclusion job currently only writes a failure summary and exits nonzero. The workflow requirement says that any failed required job must also create a GitHub issue with the failed job names and run link.
Required updates
- When
buildorintegrationfails or is cancelled, haveconclusioncreate an issue naming each failed job and linking the workflow run. - Grant only the issue-writing permission needed by the conclusion job; keep other jobs read-only.
- Pin any added GitHub Action to a commit SHA, following repository conventions.
- Keep the existing conclusion outcome aggregation and clear step summary.
Review notes
The conclusion job already depends on both required jobs with if: always() and computes their results, so it has the necessary context to report failures. It currently has only contents: read permission and ends with a step that exits 1 when either result is not success; there is no issue-creation step.
The workflow also has a named scenario matrix and several valuable PATH, shell, environment, Unicode, mixed-slash, PATHEXT, and hang checks. When updating it, review that the matrix and explicit invocation checks continue to cover the required shell, launch mode, environment shape, and path-style dimensions.
References
- Reviewed in §37415575009.
Generated by 🪟 Daily Windows Terminal Integration Builder · codex · gpt60 · 58.7 AIC · ⌖ 27.1 AIC · ⊞ 15K · ◷
Activity
pelikhan commentedon Oct 10, 2026
Duplicate of #66822, fixed by #67410 (merged). That PR adds least-privilege (
issues: writescoped to theconclusionjob only) failure-issue reporting with dedupe (comments on an existing open tracking issue instead of creating a new one), includes the failed job names and run URL, and replaces the hand-picked scenario matrix with a systematically generated one covering every shell × launch-mode and env-shape × path-style combination (32 scenarios). Closing as duplicate.