GitHub actions are deprecating the previous set-output approach for setting outputs in favour of echoing to GITHUB_OUTPUT (link) as flagged by @stephenandary in #180.
When run inside a dev container, the GITHUB_OUTPUT location is not accessible (even if the environment variable is set).
Proposed approach to handling this:
- mount the host's
GITHUB_OUTPUT location to /mnt/github/output inside the dev container - set the
GITHUB_OUTPUT environment variable in the container to /mnt/github/output
This could be done automatically so that this just works as expected for users of the CI action.
Additionally, this approach could be adopted for GITHUB_OUTPUT, GITHUB_STATE, GITHUB_ENV, GITHUB_STEP_SUMMARY, and GITHUB_PATH
GitHub actions are deprecating the previous
set-outputapproach for setting outputs in favour of echoing toGITHUB_OUTPUT(link) as flagged by @stephenandary in #180.When run inside a dev container, the
GITHUB_OUTPUTlocation is not accessible (even if the environment variable is set).Proposed approach to handling this:
GITHUB_OUTPUTlocation to/mnt/github/outputinside the dev containerGITHUB_OUTPUTenvironment variable in the container to/mnt/github/outputThis could be done automatically so that this just works as expected for users of the CI action.
Additionally, this approach could be adopted for
GITHUB_OUTPUT,GITHUB_STATE,GITHUB_ENV,GITHUB_STEP_SUMMARY, andGITHUB_PATH