You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
github/gh-aw#68816 — multi-repository checkout list expansion now requires an explicit literal multi: true per checkout entry (introduced in github/gh-aw#68593). Omitted/false keeps single-repo behaviour; literal repo lists without multi: true are rejected at compile time.
Proposed test
Workflow file: test-copilot-checkout-multi.md
Trigger: workflow_dispatch
Engine: copilot
Safe output: noop (or create-issue reporting the checked-out paths)
Variant: standard (the side repo is used as a checkout target, not as the safe-output target)
Minimal test prompt sketch
Frontmatter declares a checkout: entry with multi: true, allowed-repos containing githubnext/gh-aw-side-repo, and a path prefix. The agent lists the checked-out directories and reports that the side repo is present via noop/create-issue. A samples: block makes it deterministic.
New fixtures or secrets needed
None expected beyond githubnext/gh-aw-side-repo (existing). Confirm the PAT can read the side repo for checkout.
Notes
No existing test covers checkout: multi-repo mode; no overlap with open suggestions.
A compile-time negative case (repo list without multi: true must fail) is better as a separate rejection test, similar to test-copilot-set-issue-field-builtin-rejection.
Exact frontmatter syntax should be confirmed against the gh-aw checkout reference docs before writing the workflow, so this is filed as an issue rather than a PR.
Activity