Suggested test: copilot/restore-memory-custom-job

[github-actions]

Motivation

Link to gh-aw PR: github/gh-aw#44037 — Add restore-memory step injection for custom jobs.

Before this PR, memory stores (cache-memory, repo-memory, comment-memory) were only restored in the agent job. This change adds a new restore-memory: field for jobs.<job-id>, allowing orchestrator jobs to access memory state before the agent runs. There is currently no E2E test that exercises this new frontmatter field.

Proposed test

• Workflow file: test-copilot-restore-memory-custom-job.md
• Trigger: workflow_dispatch
• Engine: copilot
• Safe output: create-issue
• Variant: standard

Minimal test prompt sketch

Define a custom orchestrator job (e.g. jobs.setup) with restore-memory: {cache-memory: true}. Have the agent job depend on it (via jobs.agent.needs: [setup]). Ask the agent to create an issue confirming that the cache-memory directory was accessible in the setup job. This exercises the new step injection path introduced in gh-aw#44037.

New fixtures or secrets needed

None. Uses the existing githubnext/gh-aw-test repository. Requires a cache entry to be pre-populated or the test can assert the directory exists even when empty.

Notes

The feature is closely related to gh-aw#44015 (memory stores in on.steps pre-activation) and gh-aw#43984 (step ordering fix). Testing restore-memory in a custom job is the most direct regression path for gh-aw#44037 and is orthogonal to the existing test-copilot-gh-steps test.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by 🔍 Suggest New E2E Tests · 74.7 AIC · ⌖ 8.3 AIC · ⊞ 5.6K · ◷