You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently act sets the workdir (and thus GITHUB_WORKSPACE env var) for its created containers to the current dir which act is called from.
On certain platforms/scenarios this can lead to awful long paths also with possible unicode/etc. Making use of jobs.steps[].run.working-directory only partially solves the issue since there are incompatibilities with other actions such as reported in actions/checkout#197 .
Would be nice to be able to configure in .actrc the workdir/GITHUB_WORKSPACE used when it creates containers. In the past it was fixed to /github/workspace and then it was updated to use the current dir. Would be nice to be able to actually specify it.
The text was updated successfully, but these errors were encountered:
I would also like to have a way to configure this.
The Action SonarSource/sonarcloud-github-action parses code coverage files(which contain absolut file paths) and on github its always using /github/workspace making it needed to have a step which changes paths accordingly.
Act version
0.2.48
Feature description
Currently act sets the workdir (and thus
GITHUB_WORKSPACE
env var) for its created containers to the current dir which act is called from.On certain platforms/scenarios this can lead to awful long paths also with possible unicode/etc. Making use of
jobs.steps[].run.working-directory
only partially solves the issue since there are incompatibilities with other actions such as reported in actions/checkout#197 .Would be nice to be able to configure in .actrc the workdir/GITHUB_WORKSPACE used when it creates containers. In the past it was fixed to
/github/workspace
and then it was updated to use the current dir. Would be nice to be able to actually specify it.The text was updated successfully, but these errors were encountered: