Suggested test: copilot/repo-memory-concurrent-retry #18588

Motivation

github/gh-aw#63497 — Fixed push_repo_memory retry-head refresh to use the authenticated repo URL instead of unauthenticated origin, since git ls-remote origin fails on private/internal repos and previously prevented rebase-and-retry reconciliation for concurrent writers.

Proposed test

• Workflow file: test-copilot-repo-memory-concurrent-retry.md
• Trigger: workflow_dispatch (dispatched twice concurrently, similar to test-copilot-cache-memory-concurrent-merge)
• Engine: copilot
• Safe output: create-issue
• Variant: standard

Minimal test prompt sketch

Two concurrent dispatches each append a distinct marker line to a file under the repo-memory branch/store; both agents create an issue reporting all distinct markers currently present, verifying neither write was lost to a retry/rebase failure.

New fixtures or secrets needed

None — reuses the existing repo-memory tool and githubnext/gh-aw-test fixture. May need harness support (in e2e.sh) to dispatch two instances in parallel with distinct marker inputs, mirroring the existing cache-memory-concurrent-merge pattern.

Notes

test-copilot-repo-memory.md already exists but only exercises a single sequential write/read — it does not exercise the concurrent-writer retry path this fix addresses. Overlaps conceptually with test-copilot-cache-memory-concurrent-merge.md (dual-dispatch pattern) but targets the repo-memory backend instead of cache-memory. Open question: whether the harness's parallel-dispatch orchestration for cache-memory can be reused directly or needs adaptation for repo-memory's branch-based storage.

Generated by 🔍 Suggest New E2E Tests · copilot · auto · 89.8 AIC · ⌖ 7.11 AIC · ⊞ 8.5K · ◷