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
build or integration fails or is cancelled, have conclusion create 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
Generated by 🪟 Daily Windows Terminal Integration Builder · codex · gpt60 · 58.7 AIC · ⌖ 27.1 AIC · ⊞ 15K · ◷
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
conclusionjob 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
buildorintegrationfails or is cancelled, haveconclusioncreate an issue naming each failed job and linking the workflow run.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 onlycontents: readpermission and ends with a step that exits 1 when either result is notsuccess; 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