feat: add multi-play tasks.yml support and --play filter#228
Merged
josegonzalez merged 2 commits intomainfrom Apr 29, 2026
Merged
feat: add multi-play tasks.yml support and --play filter#228josegonzalez merged 2 commits intomainfrom
josegonzalez merged 2 commits intomainfrom
Conversation
Each entry in tasks.yml now executes as its own play with optional name, tags, when, and inputs. Apply and plan gain --play to scope a run to a single play; apply gains --fail-fast to revert to the legacy abort-entire-run semantics so the default becomes "abort the current play and continue to the next." Per-play inputs slot into the variable precedence chain between file-level defaults and --vars-file values. The per-play when: predicate evaluates against the file-level merged context only, so a play cannot see its own or sibling plays' play-local inputs. Single-play files keep the legacy ==> Play: tasks header unchanged.
josegonzalez
deleted the
208-add-multi-play-tasks-yml-support-and-play-filter
branch
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
1 participant
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.
Each entry in tasks.yml now executes as its own play with optional name, tags, when, and inputs. Apply and plan gain --play to scope a run to a single play; apply gains --fail-fast to revert to the legacy abort-entire-run semantics so the default becomes "abort the current play and continue to the next." Per-play inputs slot into the variable precedence chain between file-level defaults and --vars-file values. The per-play when: predicate evaluates against the file-level merged context only, so a play cannot see its own or sibling plays' play-local inputs. Single-play files keep the legacy ==> Play: tasks header unchanged.
Closes #208.