Andrey Nering

@leaanthony We've been avoiding requiring CGO in the codebase, if possible. It seems that fsnotify does not support recursive watch as well. It's in the roadmap since 2024: https://github.com/fsnotify/fsnotify/issues/18. So,...

Thanks for opening this issue! Some small comments: - `CLI_ARGS` is intentionally a string, so it's as easy as possible to delegate arguments like `yarn {{.CLI_ARGS}}`. We should keep it...

Hi @sirenkovladd, The problem with your Taskfile is that `deps` run in parallel, so it can happen that `lint` runs before `build` in your example. Changing it to run sequentially...

Unfortunately, this is a breaking change. This means we'd have to wait for the next major version release to do this by default, and that can take quite some time...

@jaedle I'm sure that some people like and use the current behavior. So, if you're willing to work on it, I think we should have a setting on the Taskfile...

Hi @hans-d, Agreed. This should be simple to implement, so I added the `good first issue` label in case anyone wants to contribute.

This was just implemented on #1762.

Hi @aminya! First of all, thanks for your contribution! After a quick look, the code itself seems to go in the right direction. As said in comments like https://github.com/go-task/task/issues/548#issuecomment-941679515, https://github.com/go-task/task/issues/455#issuecomment-890527159...

Hi @aminya, I'm sorry for the wait! I know many months have passed. The thing is just that this project demands more work than we actually have to dedicate to...

Hi @LittleC and @smyrman, Couple of things to discuss here. First: yes, it's by design that all variables are evaluated on each task run, even global ones. Perhaps that can...