New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify the meaning of "current working directory" in the readme #87
Comments
It doesn't appear that it respects the default working directory? https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#defaults |
Misleading indeed, had that problem myself. |
Ran across the default working-directory issue myself.
|
Describe the bug
The readme says "Relative and absolute file paths are both allowed. Relative paths are rooted against the current working directory", but this doesn't mean the current working directory as reported by
pwd
, but the working directory of the job.Version
Environment
Run/Repo Url
This run finishes with a warning because the file cannot be found, even though the previous step changed the working directory to the directory containing the artifact
This run(absolute) and this run (relative) finish correctly, because the relative path is relative to the starting directory of the job
How to reproduce
Add a
run
step before this step that changes the working directory viacd
The text was updated successfully, but these errors were encountered: