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
First of all, thanks for making such a neat tool, I found it very easy migrating to go-task from my archaic bash scripts. I did, however, run it one small issue with requires.env and dotenv task properties. When I load a variable from one of the files defined in dotenv array and try to verify that it's present by specifying it in requires.env it fails regardless if the variable is present in env file or not. This only happens when both properties are defined on a task level, when dotenv is defined at the root the check works as expected.
First of all, thanks for making such a neat tool, I found it very easy migrating to go-task from my archaic bash scripts. I did, however, run it one small issue with
requires.env
anddotenv
task properties. When I load a variable from one of the files defined indotenv
array and try to verify that it's present by specifying it inrequires.env
it fails regardless if the variable is present in env file or not. This only happens when both properties are defined on a task level, whendotenv
is defined at the root the check works as expected.The text was updated successfully, but these errors were encountered: