Add conditional step execution in YAML workflows #12
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
Implement ergonomic conditional execution for workflow steps:
- Add `if` field to StepDefinition as alias for `condition.expression`
- Add template pre-processor to resolve {{.steps.id.field}} references in expressions
- Add step ID validation at parse time to catch errors early
- Enforce strict boolean evaluation with nil-as-false semantics
- Update skipped step output format to match specification
- Include comprehensive documentation and example workflows
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.
Summary
iffield as ergonomic alias forcondition.expression{{.steps.id.field}}syntax in expressionsTest plan
iffield parsing and normalizationImplements SPEC-7