Wes McNamee
Wes McNamee
> I expect the task env to override the shell environment variables. The current behaviour is confusing. I agree. If you need access to the shell environment, there's always the...
Agreed. Either `includes` _and/or_ `tasks` should be present (not neither).
I kind of disagree that flattening should exist, as there's a couple things that I think might be confusing, how does a user reasonably figure out what tasks refer to...
I agree, task should be able to report directory in which the Taskfile it's operating on is located, though this brings into question, should it always be the parent Taskfile...
I like how ConcourseCI does this. It feels very natural and quite powerful: https://concourse-ci.org/modifier-and-hook-steps.html
May want to look at the functional options pattern over a fluent interface. https://dave.cheney.net/2014/10/17/functional-options-for-friendly-apis
This is related to #289 as, that would enable autocomplete fairly easily without making assumptions about the name of the compiled binary. Additionally autocomplete would be much more performant that...
This may be an issue with `mvdan/sh` which is the shell parser that Go is using
I'm working on a v4 that will be able to handle this functionality
Looking at this holistically, the goal of all this is to have `task` be a watcher for multiple things (requiring them to be started in parallel). Also, your have a...