Setting working directory about publish-docker-github-action HOT 9 CLOSED

I guess having workdir in checkout might take some time.
In this way I introduced it here, so that people can already work.
When it's introduced in checkout, it will be deprecated.
See https://github.com/elgohr/Publish-Docker-Github-Action/releases/tag/1.13 and https://github.com/elgohr/Publish-Docker-Github-Action#workdir

from publish-docker-github-action.

Edit: not working, the path argument just create a new directory and put the repository there

You can use the path input in the checkout step

    steps:
    - uses: actions/checkout@v1
      with:
        path: your_path

All the steps after that should use that path as the working directory

from publish-docker-github-action.

That is great @elgohr! Thanks for the follow-up and fix 👍

from publish-docker-github-action.

Thanks @elgohr!

from publish-docker-github-action.

Thank you for the request and fast response ☺️
Didn't know about the path in the checkout either. I guess we can close it?

from publish-docker-github-action.

That was quick! Thanks for the response and tip. I tried setting the path, but it seems to only append it to the path context:

/home/runner/work/myrepo/added_in_path

The actual workdir is the same (not sure about the use case for this). I did a pwd inside the action, and it lists the same content even after the path is set.

I also looked at the working-directory variable, but that doesn't seem to work with the uses statement:

https://github.community/t5/GitHub-Actions/Github-actions-working-directory-incorrectly-documented/td-p/29201

Maybe I'm missing something here, but I still cannot see another solution that to pass the path in to the action.

from publish-docker-github-action.

I'm trying to get an answer from Github whether there is a way to contribute to the checkout plugin, as this seems to be the one doing the actual checkout. At my point more actions could benefit from this, when it's in the checkout.

from publish-docker-github-action.

Sounds like a good plan. I agree that this is a feature that more would benefit from. That is why I almost took it for granted. Hence the feeling I'm missing a feature that already exist :)

from publish-docker-github-action.

Hello,

I face the same problem. My Dockerfile is generated in another step after the checkout step. So, the path input fix doesn't work for my case.

The additions made by @automada makes sense for me. But I think it would be better if we can use the working-directory variable with the uses statement.

from publish-docker-github-action.