Pete Davison

@TheKangaroo What shell are you using? ~~I can replicate this on `zsh`. If you're also on `zsh` then a temporary fix for you is to just comment out the following...

@TheKangaroo I've just tried this again with ZSH and it now seems to be working for me without any changes. Not sure what changed. Could you confirm what shell you're...

> a generic "runtime", which could be containers (docker, podman, kubernetes), but also things like ssh, terminal or other command interfaces @trulede I lean towards this instead of integrating with...

I am not able to reproduce this. Also running Arch on master and your example works fine for me: ``` ├── .env └── Taskfile.yml ``` ```ini # .env VAR=test ```...

@endorama That's interesting.. I don't believe there were any changes in `v3.21.0` that would effect this, so I'm not sure why you'd be able to repro in `v3.20.0`, but not...

Closing this for now. If anyone is able to repro this, please feel free to leave a comment and we can reopen.

@c-s-w. I'm still unable to reproduce this (v3.32.0) on Linux. I used @MattiasMartens's example to test along with the following `.env` file: ```env MYVAR=foo ``` Running `task` outputs: ``` task:...

@andreynering What's the expected behaviour here? The docs do not mention that you should be able to use variables defined in a `dotenv` via the templating engine (`{{.MYENVVAR}}`) and this...

@wburningham Thanks for pointing this out. The `--yes` flag has not currently been set up to automatically accept the remote task prompts. This is definitely something we can consider in...

@oliver-helix Good idea about the root remote taskfiles. As for why your example doesn't work. I think its just a simple typo: ```diff # taskfile.yml version: '3' - include: +...