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
I think the second idea is better, because it is more explicit and seems easier to understand. I'd thought the first idea would probably be easier to implement, and possibly simpler to use.
I was looking at the issues here, having a similar use-case, where I would like to change the behavior of a dependency/requirement depending on which task it triggers.
The second solution could work, but I was more thinking of inheriting environment variables of parent tasks, but since this could break existing setups, maybe introduce the concept of "global" environment variables, which could both be set directly under the ## Tasks, and overridden per task for itself and the required tasks/dependencies it would trigger.
Given:
X
with zero or more inputsY
with one or more inputsrequires
relationship fromX
toY
When:
X
with inputs needed for taskY
Then:
Y
should have access to inputs provided when running taskX
For example, given a readme:
Tasks
y
Inputs: v
x
Requires: y
this invocation will work:
v=hello xc x
but this one will fail:
xc x hello
Likewise, this readme will also fail in the same way as described above:
Tasks
y
Inputs: v
x
Inputs: v
Requires: y
The text was updated successfully, but these errors were encountered: