Cache restore seemingly ignoring `path` key
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
With this config:
I'm seeing this output:
https://github.com/oro-os/toolchain/actions/runs/13199758383/job/36848893839#step:4:28
It seems that the tarball is being extracted in the root of the repository, regardless of what the path key states, causing 100% cache miss rates.
Am I missing something? Does this not support absolute/out-of-tree paths?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/build.yml lines 24-29 and the linked Actions run log, comparing the configured path with the extraction location shown in the output. Reproduce the restore using an absolute or out-of-tree path and establish whether the path is supported or ignored; done when the behavior is fixed or the supported limitation is clearly resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100