with-checkout-path.yml

name: "Use a custom `checkout_path`"
description: "Checks that a custom `checkout_path` will find the proper commit_oid"
# Build tracing currently does not support Windows 2022, so use `windows-2019` instead of
# `windows-latest`.
# Must test on all three platforms since this test does path manipulation
os: [ubuntu-latest, macos-latest, windows-2019]
steps:
  # Check out the actions repo again, but at a different location.
  # choose an arbitrary SHA so that we can later test that the commit_oid is not from main
  - uses: actions/checkout@v2
    with:
      ref: 474bbf07f9247ffe1856c6a0f94aeeb10e7afee6
      path: x/y/z/some-path
  - uses: ./../action/init
    with:
      tools: ${{ steps.prepare-test.outputs.tools-url }}
      # it's enough to test one compiled language and one interpreted language
      languages: java,javascript
      source-path: x/y/z/some-path/tests/multi-language-repo
      debug: true

  - name: Build code
    shell: bash
    run: x/y/z/some-path/tests/multi-language-repo/build.sh
  - uses: ./../action/analyze
    with:
      checkout_path: x/y/z/some-path/tests/multi-language-repo
      ref: v1.1.0
      sha: 474bbf07f9247ffe1856c6a0f94aeeb10e7afee6
      upload: false
    env:
      TEST_MODE: true
  - uses: ./../action/upload-sarif
    with:
      ref: v1.1.0
      sha: 474bbf07f9247ffe1856c6a0f94aeeb10e7afee6
      checkout_path: x/y/z/some-path/tests/multi-language-repo
    env:
      TEST_MODE: true

  - name: Verify SARIF
    run: |
      cat ../results/java.sarif
      echo '------------------------------------'
      echo '------------------------------------'
      echo '------------------------------------'
      echo '------------------------------------'
      cat ../results/javascript.sarif