GitHub Actions working-directory is ignored on a uses step
working-directory sets the cwd for a run step’s shell. It is not a valid modifier for a uses step - actions decide their own working directory, usually via an input - so setting it on a uses step is silently ineffective.
What this error means
An action runs against the repo root instead of the intended subdirectory despite a working-directory set on the uses step.
- uses: some/build-action@v1
working-directory: packages/app # ignored on a uses stepDiagnose it: print the context before you change anything
Most workflow-expression bugs are not syntax errors, they are an expression reading something that is empty. GitHub resolves a missing property to an empty string instead of failing the run, so a wrong reference looks like a logic bug rather than a mistake. Dump the contexts first and you will usually see the answer immediately.
- name: Dump contexts
run: |
echo '--- github ---' ; echo '${{ toJSON(github) }}'
echo '--- needs ---' ; echo '${{ toJSON(needs) }}'
echo '--- steps ---' ; echo '${{ toJSON(steps) }}'
echo '--- matrix ---' ; echo '${{ toJSON(matrix) }}'
echo '--- inputs ---' ; echo '${{ toJSON(inputs) }}'Check the context is allowed where you used it
Contexts are not available everywhere. The same expression can be valid in a step if and invalid in a job if, which is why an expression that works in one workflow fails when moved.
| Where you wrote it | Contexts available there |
|---|---|
run-name | github, inputs, vars |
concurrency | github, inputs, vars |
Top-level env | github, secrets, inputs, vars |
jobs.<id>.if | github, needs, vars, inputs |
jobs.<id>.steps.if | github, needs, strategy, matrix, job, runner, env, vars, steps, inputs |
jobs.<id>.outputs | Full access, including secrets |
Reusable workflow outputs | github, jobs, vars, inputs |
Common causes
working-directory only applies to run
It controls the shell cwd for run steps; uses steps do not honor it.
Action expects a path via its own input
Most actions take a path/working-directory input instead of the step-level key.
How to fix it
Pass the directory through the action input
- Check the action’s inputs for a path or working-directory input.
- Provide the subdirectory via with.
- uses: some/build-action@v1
with:
working-directory: packages/appWrap with a run step if no input exists
- If the action has no path input, do the work in a run step where working-directory applies.
- Or cd into the directory inside a run step before invoking the tool.
Catch it before it reaches CI
Every failure in this cluster is statically detectable. actionlint parses workflow expressions, checks context availability against the same rules above, and validates needs references, so these bugs never need to cost you a run.
# one-off
docker run --rm -v "$(pwd):/repo" --workdir /repo rhysd/actionlint:latest -color
# as a job, before anything expensive runs
- uses: actions/checkout@v4
- run: |
bash <(curl -s https://raw.githubusercontent.com/rhysd/actionlint/main/scripts/download-actionlint.bash)
./actionlint -colorHow to prevent it
- Reserve working-directory for run steps.
- Consult an action’s inputs for path handling.