fix: CLI variables should take priority over Taskfile defaults #2589
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #2588
When using
task FOO=barwith a Taskfile containingFOO: '{{.FOO | default "foo"}}', the CLI value was being overwritten by the Taskfile default.The ReverseMerge function was incorrectly allowing Taskfile variables to overwrite CLI globals. Now it skips variables that already exist in the CLI globals, ensuring user-provided values take priority while still making CLI globals available for templating.
Fixes regression introduced in #2403.