Suggested test: copilot/generated-job-needs

Start with the proposed test-copilot-generated-job-needs.md workflow and compare its structure with existing standard workflow_dispatch fixtures. Configure the copilot engine, create-issue safe output, and explicit jobs: { agent: { needs: [activation] } } frontmatter, then dispatch it. Done means the workflow completes without rejecting needs, the lockfile remains valid, and the agent creates the confirmation issue.

Motivation

Link to the gh-aw PR: github/gh-aw#43940 — Allow jobs.<generated>.needs to augment compiler-generated job dependencies

Previously the compiler ignored jobs.<generated>.needs in frontmatter, so authors could not explicitly add extra dependencies to compiler-generated jobs (activation, agent, detection, safe_outputs, conclusion). This feature is now supported additively.

Proposed test

• Workflow file: test-copilot-generated-job-needs.md
• Trigger: workflow_dispatch
• Engine: copilot
• Safe output: create-issue
• Variant: standard

Minimal test prompt sketch

Compile a workflow whose frontmatter explicitly sets jobs: { agent: { needs: [activation] } } — an augmentation that is a no-op in terms of correctness but exercises the new merge path. If the compiler silently drops or rejects the explicit needs, the lockfile will differ or the run will error. The agent creates an issue confirming the run completed.

New fixtures or secrets needed

None — this is a pure frontmatter/compiler feature exercised within the standard workflow_dispatch path.

Notes

Open question: which explicit needs augmentation produces a meaningfully distinct lockfile vs just repeating a compiler-inferred edge. A simple smoke-test (add an explicit dep the compiler would have inferred anyway and verify no error/no rejection) is sufficient for a first regression. Cross-engine variants (claude/codex) can follow once the copilot variant is green.

[!WARNING]

Firewall blocked 1 domain

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

• awmgmcpg

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

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by 🔍 Suggest New E2E Tests · 41 AIC · ⌖ 6.66 AIC · ⊞ 5.6K · ◷