Skip to content

[windows-integration] Update windows-cli-integration workflow to use safe issue creation and strengthen matrix-driven chaos assertions #62312

Description

@github-actions

Summary

The existing .github/workflows/windows-cli-integration.yml already implements most required behavior (daily schedule + dispatch, multi-job orchestration, Ubuntu build artifact, Windows integration checks, broad shell/environment/path chaos coverage, timeout protections, and an if: always() conclusion job).

However, it still needs updates to fully satisfy repository/runtime constraints and improve debuggability guarantees.

Required updates

  • Replace gh issue create in the conclusion job with a repository-approved write path (safe-outputs based issue declaration) because cloud-agent runs must use safe outputs for GitHub writes.
  • Keep permissions minimal while preserving ability to create failure issues.
  • Preserve existing job structure and current scenario coverage.
  • Add clearer failure diagnostics around matrix scenario identity and timeout context so shell-specific hangs are immediately attributable.
  • Ensure at least one intentionally adversarial negative chaos case remains explicitly asserted as fast-failing and debuggable in step summary output.

Why this is needed

  • Current conclusion behavior performs a direct GitHub write via gh issue create, which is incompatible with the run constraints requiring safe-output write intents.
  • Existing matrix and timeout scaffolding are strong, but failure attribution can be more explicit for rapid triage.

Acceptance criteria

  • conclusion job still runs with if: always() and fails workflow when required upstream jobs fail.
  • On failure, workflow records failed job names and creates a GitHub issue through approved safe-output mechanism (not direct gh issue create).
  • Integration checks continue to cover shell × launch mode × env shape × path style matrix and include explicit timeout/hang detection.
  • Logs/step summary clearly identify failed scenario dimensions.
  • No unrelated workflow files are changed.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

  • ab.chatgpt.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "ab.chatgpt.com"

See Network Configuration for more information.

Generated by 🪟 Daily Windows Terminal Integration Builder · codex · gpt53codex · 6.95 AIC · ⌖ 3.54 AIC · ⊞ 14K · ◷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions