Skip to content
Discussion options

You must be logged in to vote

Hi @PavelVydysh, yes this is by design. The do tasks are designed to be either:

  • all inline, then they're treated as a single workflow path
  • all nested, then they're treated as multiple workflows (see example)

The reality is that there is a bit of a rough edge here that the code has to make a couple of assumptions and it does it by going on the order the tasks are presented in, which is what you're seeing. See the code for the how.

In reality, you shouldn't be putting a nested do task in a workflow. You can achieve what you want by removing the nested do:

.anchors:
  # A flat task list. Every task here is a sibling in the SAME scope, which is
  # what keeps this a single registered workfl…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by PavelVydysh
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants