Skip to content

Suggested test: copilot/checkout-multi-repository-explicit-opt-in #22852

Open

Description

@github-actions

Motivation

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.

Generated by 🔍 Suggest New E2E Tests · copilot · auto · 14.5 AIC · ⌖ 0.538 AIC · ⊞ 8.7K · ◷

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions