Skip to content

samples mode: call-workflow replay drops the workflow name #55176

Description

@dsyme

Summary

In samples mode, the dynamically generated call-workflow MCP tool now registers and replays, but the emitted canonical call_workflow message omits its workflow identity. The apply job rejects it with Workflow name is empty.

Follow-up to the call-workflow portion of #54811.

Evidence

Workflow sample:

samples:
  - workflow_name: "test-copilot-call-worker"
    inputs:
      sentinel: "${{ github.event.inputs.sentinel }}"

At github/gh-aw commit eaca36f, the replay server registers test_copilot_call_worker with metadata workflow: test-copilot-call-worker. apply_samples calls it with the sentinel and reports success. The apply stage then finds one call_workflow message but fails:

Workflow name is empty, skipping
Message 1 (call_workflow) failed: Workflow name is empty

The dynamic handler needs to materialize its _call_workflow_name metadata into the canonical field consumed by the apply handler, while preserving the sample inputs.

Parent: https://github.com/githubnext/gh-aw-test/actions/runs/32615153966
Child: https://github.com/githubnext/gh-aw-test/actions/runs/32616131682

Activity

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingmcp

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions