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
Describe the bug
In a condition_script, the cwd value of the task isn't used. This was a little counter-intuitive and took me a bit to figure out. It's easy to work around by cding in the script, but I'd expect it'd use the task cwd. If not, I think the docs should probably mention this in the section about condition_scripts.
Additionally, the condition script won't get the values of anything set in env for that task, which I think makes some sense, but would also be nice to call out in the doc.
To Reproduce
Make a task with a non-root cwd and a condition_script. The working dir for the condition script will be the root directory of the project.
@Sushisource ya cwd not impacting the condition script is a bug. will fix that.
env i would prefer to keep as is, as it is 'invocation' of the task same as its command/script and should only happen if conditions are met.
I'll update the docs as you recommended. thanks
Describe the bug
In a
condition_script
, thecwd
value of the task isn't used. This was a little counter-intuitive and took me a bit to figure out. It's easy to work around bycd
ing in the script, but I'd expect it'd use the task cwd. If not, I think the docs should probably mention this in the section about condition_scripts.Additionally, the condition script won't get the values of anything set in
env
for that task, which I think makes some sense, but would also be nice to call out in the doc.To Reproduce
Make a task with a non-root
cwd
and acondition_script
. The working dir for the condition script will be the root directory of the project.Code Sample
Really love this tool! Thanks for your hard work!
The text was updated successfully, but these errors were encountered: