`jobs.<job_id>.steps[*].working-directory` doesn't say it's incompatible with `uses`

[jsoref]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idstepsworking-directory

What part(s) of the article would you like to see updated?

Using the working-directory keyword, you can specify the working directory of where to run the command.

- name: Clean temp directory
  run: rm -rf *
  working-directory: ./temp

It doesn't actually say that it only works for run: commands. And it doesn't explain what would happen if you use a uses: command that's implemented as a composite action.

Additional information

Apparently the languageservices code believes that working-directory is only valid for run-step things: https://github.com/actions/languageservices/blob/fb5c6e4f27bb1ddf512609a6a341aadd17ce86f3/workflow-parser/src/action-v1.0.json#L339-L372

[Sharra-writes]

@jsoref This is one for the Actions team. There's still a backlog on that, but I'll get it in front of them when I'm able to.

[github-actions]

A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.

[github-actions]

A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.

[christiandouka-blip]

Hi! I would like to work on this issue. I plan to update the jobs.<job_id>.steps[*].working-directory documentation to clarify that working-directory applies to run steps and is not supported with uses steps. I will keep the change focused on the documentation described in this issue.

[jsoref]

@christiandouka-blip this issue isn't open to external contributors. Please see https://github.com/github/docs/labels?q=help