Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is concerned with behavior when multiple task files are
include:-ed with explicitdir:and use dynamicsh:vars.t2.envis not being merged intot1root -> parent -> A/Bincludes, the outer merge overwrites.dir:-specific caching ofsh:dynamic vars (e.g. now multiplefind . -name '*.md'is possible)4.
taskRangeFuncshould resolvet.Dirat call time, not construction time, sodir: '{{.VAR}}'variables are availableAssuming I ran it properly, the test suite passes, my minimal repro steps are resolved, and my original bug report scenario is fixed.
I am not a go programmer, this PR was overwhelmingly AI-written, I have no idea if these changes are terrible ideas, but I hope they clarify what might be going wrong in #2753
fixes #2753