peptiderepo da79ee234f fix(ci): explicitly checkout peptide-e2e in workflow_call context ...

When smoke.yml runs via workflow_call from another repo (peptide-repo-core,
peptide-starter-theme, etc.), GitHub Actions checks out the CALLER's repo
by default. The caller has no package-lock.json, so setup-node's npm cache
lookup fails with 'Some specified paths were not resolved'.

Fix: add repository/ref to the checkout step so we always fetch peptide-e2e
regardless of who calls the workflow. This ensures npm ci and Playwright
have the correct test code and dependency lockfile.

2026-04-27 15:37:34 +00:00

2.2 KiB

Executable File

Raw Blame History

View Raw