On the Mac runner, I’m seeing that I cannot depend on the location of GITHUB_WORKSPACE to be the same from job to job.
This is particularly problematic for two reasons. First, when combined with the
actions/cache action, it prevents successful caching of objects outside of
GITHUB_WORKSPACE, because the tar manifest is using relative paths from that directory as root.
And even if that were not an issue—let’s say I choose never to cache anything outside of GITHUB_WORKSPACE—I cannot build anything that depends on the absolute path. Unfortunately, for instance, conda environments are not relocatable, so that prevents me from creating conda environments that are cached.
Yes, I know Miniconda is included, but I’m actually testing conda-specific tooling and as such I need to create my own conda installation.