Andrey Nering
Andrey Nering
This sounds like an easy one. Open for community pull requests.
Hmm... I didn't give this a lot of thought when assigned as a bug. Yeah, the current behavior is probably by design, but we can still consider improving it. No...
Hey @trulede! First of all, thanks for your patience! I know if have many PRs opened and we are overdue on reviewing them. I debugged this flaky test a little...
Hi @leaanthony. I'm sorry, I know I'm late on many reviews. I'll add this to my TODO list. In the meantime, can you rebase? Also, can you write a short...
Users should avoid having conflicting variable names for now, and we should attempt to make it Taskfile scoped in the future. I'm not 100% sure how things worked before DAG....
Hi @jamestenglish. No such feature exists yet, but I'll keep this issue as an idea that can be implemented in the future.
As an alternative, you could [set environment variables globally using `env:` on your `Taskfile.yml`](https://taskfile.org/#/usage?id=environment). That wouldn't allow you to use `Taskvars.yml`, though.
Ping @jamestenglish Does the proposed solution work for you? I think it's actually cleaner than what you proposed. Thoughts?
Hey @jamestenglish, It's intentional that the variable precedence order is as is. It's from top to lower level, and as @smyrman, this kinda mimic how function calls would work. That...
Hi again @jamestenglish, So... some people have started to ask for some stuff that requires minor/small breaking changes to Task. This variable priority thing is one of them. That said,...