Support `working-directory`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Per the title it would be great if this supported working-directory to set the folder where you are running code for a step
- name: Save ${{ inputs.target }}
if: always()
working-directory: ${{ inputs.workdir }}
uses: actions/cache/save@v4.2.0
with:
path: "file.tar.gz"
key: ${{ inputs.target }}-corpus-${{ github.run_id }}
The path is so strict that when folder structure is not always static it makes working with save / restore very difficult.
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
No files, tests, or entry points are named in the issue. Start by locating the cache save and restore action inputs and path handling, then verify that a working-directory input scopes relative paths as shown in the example without changing existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100