Tasks - Sources relative to cwd, not config_root, per docs #4596
Unanswered
andrew-womeldorf
asked this question in
Troubleshooting and bug reports
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
According to the tasks docs for sources:
Configuration
Expected
From within any directory in the project, I can execute
mise watch -t foo
, and thefoo
task will trigger anytime I make a change tocmd/foo/main.go
.Actual
mise watch -t foo
from the project root,foo
task is triggered when I modifycmd/foo/main.go
👍 :mise watch -t foo
from a nested directory, such ascmd
,foo
task is not triggered when I modifycmd/foo/main.go
. 👎Discussion
So the paths are relative to CWD, but not the config root.
Additionally, using absolute paths with
{{config_root}}
doesn't seem to work either:running with debug logging (
mise watch -t foo -v),
watchexec` is using the absolute path I expect, but the task is still not being triggered when the go file changes.Beta Was this translation helpful? Give feedback.
All reactions