mirror of
https://github.com/nektos/act.git
synced 2026-04-27 01:45:52 +03:00
[GH-ISSUE #1134] Enhancement: support for setting working directory in container #641
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#641
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jacob-carlborg on GitHub (Apr 19, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1134
Describe feature
I would like to be able to set the working directory inside the container which is running the workflows. Currently Act is using the full path of the working directory where the
actcommand is run, as the working directory inside the container. This usually does not match the working directory when a workflow is run on github.com. I would like the environment Act is using to run the workflows to be as similar as possible to the environment on github.com.@catthehacker commented on GitHub (Apr 21, 2022):
We don't use same path due to some issues we had, but you shouldn't hard-code GitHub runner paths. It's recommended to always use contexts and environment variables. Other than that, initial working directory doesn't really matter.