Hack entrypoint to work around Actions setting the working dir #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since this Action is in a private repository, you must clone it manully first and then call the Action. However, since you have to clone the repository into an alternate directory, Actions will start the Docker container with the working directory being that of the calling workflow repository. Example here: https://github.com/github/ci-hello-world/runs/6396135283?check_suite_focus=true#step:5:47 The workdir is set to `--workdir /github/workspace`. This doesn't work because the go files are actually in `/`. Since the go files are in fact in `/` we can just cd to that directory. I believe this worked implicitly within this repository because the go files happened to also be found into the working directory Actions was setting.
hosom
approved these changes
May 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since this Action is in a private repository, you must clone it manually first and then call the Action.
However, since you have to clone the repository into an alternate directory, Actions will start the Docker container with the working directory being that of the calling workflow repository.
Example here:
https://github.com/github/ci-hello-world/runs/6396135283?check_suite_focus=true#step:5:47
The workdir is set to
--workdir /github/workspace.This doesn't work because the go files are actually in
/. Since the go files are in fact in/we can just cd to that directory.I believe this worked implicitly within this repository because the go files happened to also be mounted into the working directory Actions was setting.