GitHub Actions Composite Action "no such file" - Use github.action_path
A composite action fails to run a script it ships because run: steps resolve paths from the consumer's workspace, not the action's own directory. The fix is to anchor paths to github.action_path.
What this error means
A composite action calls its own helper script (e.g. ./scripts/setup.sh) and fails with "No such file or directory", because the relative path is resolved from the caller's checkout, not the action.
# inside the composite action.yml
- run: ./scripts/setup.sh
shell: bash
# fails: ./scripts is looked up in the CONSUMER's workspace, not the actionDiagnose 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
run: paths resolve from the workspace
In a composite action, run: steps execute with the consumer's working directory. A relative path to a file shipped inside the action does not exist there.
Action not checked out alongside its scripts
Bundled scripts live wherever the action was downloaded. Without github.action_path you have no stable way to reference them.
How to fix it
Anchor paths to github.action_path
Reference the action's own directory via the github.action_path context so bundled files resolve regardless of the consumer's workspace.
runs:
using: composite
steps:
- run: "${{ github.action_path }}/scripts/setup.sh"
shell: bashMake scripts executable and portable
- chmod +x the bundled scripts (or invoke them via bash <path>).
- Use github.action_path for every file the action ships.
- Avoid assuming the consumer checked the action out into a known relative path.
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
- Reference bundled action files via github.action_path.
- Do not rely on relative paths to the consumer workspace inside an action.
- Ship executable scripts or invoke them through an interpreter.