githubnext / githubnext/gh-aw-test
Suggested test: copilot/aw-manifest-wildcard-include
- Dominant language
- Shell
- Stars
- 8
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
## Motivation
github/gh-aw#58545 — `aw.yml` manifests now support a single trailing `/*` wildcard in `includes:` (e.g. `workflows/*`, `agents/*`, `skills/*`), expanding to all direct children of a directory with deterministic ordering and dedup, while rejecting wildcards in other positions.
## Proposed test
- **Workflow file**: `test-copilot-aw-manifest-wildcard-include.md` (plus a small fixture directory of importable snippets)
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `create-issue`
- **Variant**: standard
## Minimal test prompt sketch
Add an `aw.yml` package manifest (or local `imports:`) that uses a trailing wildcard (e.g. `shared/mcp/*`) to pull in multiple existing shared snippets, compile it, and have the agent confirm in the created issue which imported values/tools were available — verifying the wildcard expansion actually happened at compile time.
## New fixtures or secrets needed
Likely need a new small directory of 2-3 trivial importable `.md`/config snippets under `.github/workflows/shared/` (repo already has `shared/mcp/`) to exercise the wildcard expansion; no new secrets.
## Notes
No existing test in `existing-tests.json` exercises `aw.yml`/`includes:` wildcard behavior — this is purely a compile-time feature, so the "test" is really about `gh aw compile` producing the expected lockfile; the workflow_dispatch run itself is a secondary check that the compiled output still executes normally. Consider whether this is better verified as a compile-time unit test upstream in gh-aw rather than here — flagging for triage.
> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/33955548499) · copilot · auto · 35.2 AIC · ⌖ 8.46 AIC · ⊞ 8.8K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-test+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-test%2Fsuggest-new-e2e-tests%22&type=issues)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with test-copilot-aw-manifest-wildcard-include.md and inspect existing-tests.json plus the existing .github/workflows/shared/mcp/ fixtures. Run the relevant gh aw compile flow and check the generated lockfile for deterministic wildcard expansion and deduplication. Done means the workflow_dispatch test compiles, uses the imported snippets, and executes with the expected safe output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, yaml
- Domain
- ci-cd, devtools, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100