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
However, calling any task from the root Taskfile sets TASKFILE_DIR to the root Taskfile's directory for variable resolution, leading to this error:
stat /var/folders/b8/g43jjlg51gs4h13yf49sjmjm0000gn/T/tmp.6yctrFQfZM/tasktest/foo.sh: no such file or directory
task: Command "/var/folders/b8/g43jjlg51gs4h13yf49sjmjm0000gn/T/tmp.6yctrFQfZM/tasktest/foo.sh" failed: exit status 127
Expected Behavior
{{.TASKFILE_DIR}} in the common/Taskfile.yaml file should always resolve to the common subdirectory, never to the directory of the including Taskfile. The current behavior makes it impossible for the included Taskfile to reference a file next to it (at least without knowing the relative path from including to included Taskfile).
Version
v3.41.0
Operating system
macOS (darwin/arm64)
Experiments Enabled
None
The text was updated successfully, but these errors were encountered:
Description
Setup
Taskfile.yaml
common/Taskfile.yaml
common/foo.sh
The content of this file doesn't really matter.
Actual Behavior
Calling
task shared:pwd
works as expected:However, calling any task from the root Taskfile sets
TASKFILE_DIR
to the root Taskfile's directory for variable resolution, leading to this error:Expected Behavior
{{.TASKFILE_DIR}}
in thecommon/Taskfile.yaml
file should always resolve to thecommon
subdirectory, never to the directory of the including Taskfile. The current behavior makes it impossible for the included Taskfile to reference a file next to it (at least without knowing the relative path from including to included Taskfile).Version
v3.41.0
Operating system
macOS (darwin/arm64)
Experiments Enabled
None
The text was updated successfully, but these errors were encountered: