How to write multi-line condition in if

[kei-yamazaki]

I used '>' to describe a multi-line condition in if.

I thought this would work as expected, but the combination of '>' and '${{ }}' seems to work strangely.

Below is the workflow created for confirmation.

name: condition-tests
on:

push:

branches: [ master ]
jobs:

test:

runs-on: ubuntu-latest
steps:
- name: test1
  run: echo hoge
  if: ( 'a' == 'a' )

- name: test2
  run: echo hoge
  if: ( 'a' == 'b' )

- name: test3
  run: echo hoge
  if: >
    'a' == 'a'

- name: test4
  run: echo hoge
  if: >
    'a' == 'b'

- name: test5
  run: echo hoge
  if: >
    ${{ 'a' == 'a' }}

- name: test6
  run: echo hoge
  if: >
    ${{ 'a' == 'b' }}

And the execution result is this.

image434×734 20.6 KB

I thought that the last test6 was skipped, but it is not actually skipped.

I think that there is something wrong with the Parser in GitHub Actions when I combine '>' and '${{ }}'. Is my workflow something syntactically wrong ?

[BrightRan]

@kei-yamazaki,

you need to use the symbol ‘|’ to set the multi-line condition.
For example:

jobs:
  job1:
    if: |
      github.event_name == 'push' ||
      (github.event_name == 'pull_request' && github.head_ref == 'master')

Here is a same topic as reference:

<a href="https://github.community/t/github-action-combining-if-condition-or-writing-it-in-multiple-lines/116903/2">Github action combining if condition or writing it in Multiple lines</a> <a class="badge-wrapper  bullet" href="/c/code-to-cloud/github-actions/41"><span class="badge-category-parent-bg" style="background-color: #6a737d;"></span><span class="badge-category-bg" style="background-color: #2188ff;"></span><span style="" data-drop-close="true" class="badge-category clear-badge" title="Discussion and questions about GitHub Actions—automation for all of your development workflows, now with world-class CI/CD.">GitHub Actions</span></a>

@uditgaurav, You can write like as the following: - name: Running all tests if: | startsWith(github.event.comment.body, '/run-e2e-all') || startsWith(github.event.comment.body, '/run-e2e-first-test') || startsWith(github.event.comment.body, '/run-e2e-second-test') || startsWith(github.event.comment.body, '/run-e2e-third-test') || startsWith(github.event.comment.body, '/run-e2e-fourth-test') || startsWith(github.event.comment.body, '/run-e2e-fifth-test') || startsW…

Note: if you use “${{ }}” to surround the condition, this will not work.

[andyfeller]

The use of pipes | for multi-line YAML values is covered in YAML specification for block style productions.

[kei-yamazaki]

@brightran,
Thank you for your reply.

Is it a specification that doesn’t work when using “|” and “${{ }}” together?
If so, I think it should be documented.
https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#about-contexts-and-expressions

[BrightRan]

@kei-yamazaki ,

Yes, I agree.
The documentation even does not mention using the ‘|’ symbol to declare a multi-line if conditional.

[smac89]

Just an FYI for anyone wondering:

Multiline condition works for assignment. So something like

jobs:
  job1:
    outputs:
      my-output: ${{ steps.get-latest-release.outcome == 'success' &&
                     steps.get-latest-dev.outcome == 'success' &&
                     (steps.get-latest-release.outputs.result != steps.get-latest-dev.outputs.result) }}

HTH

[frewilhelm]

[FYI to people that just found this discussion]

Note: if you use “ ${{ }} ” to surround the condition, this will not work.

In the meantime it seems to work to combine | and ${{ ... }} in multiline if-conditions (on GHE 3.0.10):

Example:

jobs:
  job_test:
    if: |
        ${{ github.event_name == 'push'
            || ( github.event_name == 'workflow_run'
                 && github.event.workflow_run.conclusion == 'success'
               ) }}

[chrisba11]

I've found that this does not actually work for me. Here are my findings:

This works as expected:

    if: |
      !cancelled() && needs.deploy.result == 'success' && 
      needs.tf-apply.result != 'failure'

This also works as expected:

    if: ${{ !cancelled() && needs.deploy.result == 'success' && needs.tf-apply.result != 'failure' }}

This does not get skipped when the workflow is cancelled and will run even when the result of the deploy job is not 'success':

    if: |
      ${{ !cancelled() && needs.deploy.result == 'success' && 
      needs.tf-apply.result != 'failure' }}

[existere]

fwilhelm92:

[FYI to people that just found this discussion]
In the meantime it seems to work to combine | and ${{ ... }} in multiline if-conditions (on GHE 3.0.10):

This did not work for me. In my case the first conditional was evaluated and did not throw an error but the second never was. In your case, having || would not throw an error either unless you tested worflow_run manually.

      - name: Set AWS Env
        if: |
          ${{ github.ref == 'refs/heads/master' 
            && (!contains(github.event.head_commit.message, 'skip-release')
              )}}

However, @brightran 's example did work:

      - name: Set AWS Env
        if: |
          github.ref != 'refs/heads/master' 
            && !contains(github.event.head_commit.message, 'skip-release')

[byam]

thanks, it works for me ;)

[brianjmurrell]

My testing just now indicates that only >- actually works when you use ${{ }}. Both of > and | do not work. Here is my if: conditional:

    if: >-
        ${{ (inputs.BRANCH != '' ||
             needs.Import-commit-pragmas.outputs.run-gha ||
             inputs.RUN_GHA ||
             github.event_name == 'workflow_dispatch') &&
            needs.Import-commit-pragmas.outputs.rpm-test-version == '' &&
            !contains(needs.Import-commit-pragmas.outputs.pr-repos, inputs.NAME) }}

when the evaluation results in false, the job is only skipped if i use the >- syntax and is not skipped when using > or |.

Note that if I remove the surrounding ${{ }} | can be used successfully.

Which I find infuriatingly stupid if I am being honest. I've gnashed for 2 days now getting to the bottom of this. Trying alternate multi-line syntax was not something I had even considered could be a cause of why my if: was not working.

[Hellseher]

It looks like GitHub Action "partly supports YAML" standard https://yaml.org/spec/1.2.2/#65-line-folding

It's vague specified in GHA documentation which version of YAML is implemented https://docs.github.com/en/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions

[kumar1708]

This is not working for me:

job:
 job-name:
    needs: [terraform]
    if: ${{ needs.terraform.outputs.has_changes == 2 && github.ref == 'refs/heads/master' && inputs.TF_WORKING_DIR == '*test' }}

After adding this condition (inputs.TF_WORKING_DIR == '*test') , workflow is not working as expected.

I have two directories:

• ./gh-snow-test
• ./git-snow-test

So, I was trying to use *test to make this work, can someone guide

[BenCoden]

I am having the same issue

[Yang-33]

You can use endsWith(inputs.TF_WORKING_DIR, 'test') https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/evaluate-expressions-in-workflows-and-actions#endswith