[bug] upload-artifact does not respect the working directory

[rodush]

What happened?

When the working directory for the whole job is changed via:

...
defaults:
    run:
        working-directory: some-directory

and the path to artefact is specified as

...
with:
    path: some-file.txt

then the Action fails to find the file.

What did you expect to happen?

Upload Artifact action should respect the "working-directory" parameter, instead of trying to resolve file from the github.workspace

How can we reproduce it?

Use the yaml snippets from the description above

Anything else we need to know?

No response

What version of the action are you using?

v2

What are your runner environments?

linux

Are you on GitHub Enterprise Server? If so, what version?

No response

[krystof-k]

Still happening in v3. Very confusing, especially with the docs as fixed in #318.

[victorlin]

This is user error. working-directory has no effect on any actions, including actions/upload-artifact. See #196.

I don't think there is a way to specify a working directory for this action.

[agostbiro]

I don't think it's user error. The readme says "[r]elative paths are rooted against the current working directory".