Skip to content

gh aw add of workflow with transitive import from nested directory fails #17620

@dsyme

Description

@dsyme

Bug from githubnext/agentics#182

Situation was

  • workflows/workflow.md imports "shared/file1.md"

  • workflows/shared/file1.md imports "shared/file2.md"

  • workflows/shared/file2.md imports nothing

  • Install via remote gh aw add githubnext/agentics/workflow fails

  • install by local gh aw compile workflows/file1.md succeeds

  • Didn't try install via local gh aw add workflows/workflow.md

Design question is whether local imports are resolved relative to directory where importing file is - should the second import be

import shared/file2.md

or

import file2.md

or

import ./file2.md

However many systems ban this and encourage some syntax rooted in top level of local situation, like

import @/shared/file2.md

We should probably do the same. Directory relative imports are a nightmare to maintain as you move files around and quite buggy to implement

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions