Accept a working-directory as an input argument

I’m trying to setup node for my GitHub Action. But I’m not working in the default directory.

I clone a repo in dir_one/rep_one and then clone another repo in dir_two/rep_two and copy a couple of files from the first repo to the second repo.

Then I want to setup Node and npm install on the second repo.

working-directory doesn’t work with uses and I also tried to - run: cd dir_two/repo_two, but again build fails because it’s running in its folder.

I receive this error:

Error: Dependencies lock file is not found in /home/runner/work/Site/Site. Supported file patterns: package-lock.json,yarn.lock

Please create an input argument to accept path where node should search for package.json file.

[Nefcanto]

Hi @dbaker-aa , thank you for that note. However, I’m not going back. Software entities are supposed to move forward and add features, not remove them. This feature should exist in this action to become a more mature action.

[maxim-lobanov]

Hello everyone!

This feature request will be implemented soon. I have a small ADR under review https://github.com/actions/setup-node/pull/299 . Proposed approach is a bit different from proposed in this issue - we would like allow specifying full path (directory path + filename) to lock file instead of working_directory (directory path only). We believe this approach will be a bit more generic and unblock more use-cases.