# This is a basic workflow to help you get started with Actions

name: CI

# Controls when the action will run. Triggers the workflow on push or pull request
# events but only for the master branch
on: [push]

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  # This workflow contains a single job called "build"
  test-compile:
    # The type of runner that the job will run on
    runs-on: ubuntu-latest
    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
    # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
    - name: Setup BATS testing framework
      uses: mig4/setup-bats@v1.0.1
    - name: Check out the code
      uses: actions/checkout@v2
    - name: Run the compiling tests
      run: |
        cd compiling
        bats bats_tests.sh
  test-clean:
    # The type of runner that the job will run on
    runs-on: ubuntu-latest
    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
    # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
    - name: Setup BATS testing framework
      uses: mig4/setup-bats@v1.0.1
    - name: Check out the code
      uses: actions/checkout@v2
    - name: Run the cleaning tests
      run: |
        cd cleaning
        bats bats_tests.sh

# This is a basic workflow to help you get started with Actions

name: CI

# Controls when the action will run. Triggers the workflow on push or pull request
# events but only for the master branch
on: [push]

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  # This workflow contains a single job called "build"
  test-compile:
    # The type of runner that the job will run on
    runs-on: ubuntu-latest
    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
    # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
    - name: Setup BATS testing framework
      uses: mig4/setup-bats@v1.0.1
    - name: Check out the code
      uses: actions/checkout@v2
    - name: Checkout sub-modules
      run: |
        git submodule init
        git submodule update
    - name: Run the compiling tests
      run: |
        cd compiling
        bats bats_tests.sh
  test-clean:
    # The type of runner that the job will run on
    runs-on: ubuntu-latest
    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
    # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
    - name: Setup BATS testing framework
      uses: mig4/setup-bats@v1.0.1
    - name: Check out the code
      uses: actions/checkout@v2
    - name: Checkout sub-modules
      run: |
        git submodule init
        git submodule update
    - name: Run the cleaning tests
      run: |
        cd cleaning
        bats bats_tests.sh

Add workflow commands to checkout submodules
Add workflow commands to checkout submodules

The new `bats-core` tests were failing on GitHub Actions because we didn't have the various `git` submodules populated. This adds commands to the workflows to fix that.