Skip to content

gh aw add does not resolve uses: references in imported files #44757

Description

@mnkiefer

When using gh aw add to install an agentic workflow package, the command correctly resolves top-level imports: blocks in the added workflow files — installing any referenced shared files. However, it does not recursively resolve uses: references found inside those shared/imported files. As a result, transitively required workflow files are silently omitted from the installation.

Current Behavior

Given an agentic workflow package with the following structure:

  • orchestrator.md declares imports: - uses: shared/control.md
  • shared/control.md declares imports: - uses: control-precompute.md and imports: - uses: control-instructions.md
  • worker.md declares imports: - uses: shared/helper.md

Running gh aw add <package>/orchestrator installs shared/control.md (resolved from the top-level imports:), but does not install:

  • shared/control-precompute.md
  • shared/control-instructions.md
  • shared/helper.md (referenced from a worker file)

Expected Behavior

gh aw add should resolve uses: references transitively — walking the full dependency tree of imports: blocks across all referenced files — so that all required shared workflow files are installed without needing to be enumerated manually in aw.yml.

Suggested Fix

Extend gh aw add's dependency resolution to recursively follow uses: entries within imports: blocks of all fetched workflow files, similar to how top-level imports: are already resolved.

Metadata

Metadata

Labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions