Open
Conversation
THis commit adds a test to check if a nested workflow is correctly skipped when the outer `when` condition returns False. In particular, it checks that `None` values are only propagated to the workflow outputs, and not to the inputs of the inner steps.
GlassOfWhiskey
force-pushed
the
skip-nested-workflow
branch
from
6f0d83b to
3b6c331
Compare
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.
This commit adds a test to check if a nested workflow is correctly skipped when the outer
whencondition returns False. In particular, it checks thatNonevalues are only propagated to the workflow outputs, and not to the inputs of the inner steps.