Similarly to #23 , when running containers directly, they will automatically mount the Github workspace and set it as the workdir for the container, so that all of the repository contents could be accessed (assuming a checkout was done).
This seems like a safe default and it'd be intuitive to keep this flow when running containers via the docker-run-action.
Changes:
Automatically mount the $GITHUB_WORKSPACE
Ability to specify the workdir for the container. Defaults to $GITHUB_WORKSPACE
Note, this change depends on #23 , since the container we are running needs to know about the Github environment variables in order to mount the correct volume for the workspace. As the action is now, we are ignoring all Github and user-defined env vars (set via env: on the step).
Similarly to #23 , when running containers directly, they will automatically mount the Github workspace and set it as the
workdirfor the container, so that all of the repository contents could be accessed (assuming a checkout was done).This seems like a safe default and it'd be intuitive to keep this flow when running containers via the
docker-run-action.Changes:
workdirfor the container. Defaults to $GITHUB_WORKSPACENote, this change depends on #23 , since the container we are running needs to know about the Github environment variables in order to mount the correct volume for the workspace. As the action is now, we are ignoring all Github and user-defined env vars (set via
env:on the step).