Skip to content

Suggested test: copilot/dispatch-workflow-work-queue #19912

Open

Description

@github-actions

Motivation

Link to the gh-aw PR: github/gh-aw#65443 — Connects safe-outputs.dispatch-workflow to the work-queue MCP so agents can claim durable Work and dispatch it to a trusted worker, injecting the claim into the worker's aw_context.

Proposed test

  • Workflow file: test-copilot-dispatch-workflow-work-queue.md
  • Trigger: workflow_dispatch
  • Engine: copilot
  • Safe output: dispatch-workflow (with work_queue selector)
  • Variant: standard

Minimal test prompt sketch

Seed a work-queue item (or use a deterministic samples: entry), then have the agent emit dispatch_workflow targeting test-copilot-dispatch-worker with a work_queue: {work_id: ...} selector, verifying the claim is attached to the dispatched run's aw_context.

New fixtures or secrets needed

Possibly a minimal work-queue seed fixture (a queue item/claim record) if the work-queue MCP requires pre-existing state; otherwise none — same-repository worker (test-copilot-dispatch-worker) already exists.

Notes

Existing test-copilot-dispatch-workflow.md only exercises plain dispatch (no queue selector). This PR adds a new boundary: queue-backed dispatch is limited to same-repository workers, and failed dispatch should cancel the claim — worth noting as a secondary assertion if feasible.

Generated by 🔍 Suggest New E2E Tests · copilot · auto · 73.5 AIC · ⌖ 5.86 AIC · ⊞ 8.5K · ◷

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