name: CI
on:
  push:
    branches:
      # To supress this action launches twice on conditions which fulfills all of follwings:
      #   - On pushing a new change to a branch.
      #   - The branch is opening a pull request
      #   - The branch is origin repository.
      # We limits for push events for `master`.
      # By [this link](https://github.community/t5/GitHub-Actions/How-to-trigger-a-single-build-on-either-push-or-pull-request/m-p/32469#M1144), 
      # we seem that we need to add `branches` for `pull_request` event.
      # However, actually, we don't have to limit a target branch for pull requests to suppress this problem.
      # Even if we don't specify it, it triggers this action that pushing to the branch for pull request.
      - master
      # These branches are used by bors-ng.
      - staging
      - trying
    tags-ignore:
      # Ignore for release/
      - v*.*.*
  pull_request:

jobs:
  build:
    runs-on: ubuntu-latest
    container: node:${{ matrix.node-version }}-buster

    strategy:
      matrix:
        node-version:
          # As my observations, Node.js 12 does not supports `exports` field.
          # This is nice to contrast.
          - 12
          - 14

    steps:
    - uses: actions/checkout@v1
  
    - name: Install dependencies
      run: yarn install

    - name: Test
      run: make test -j
      env:
        CI: true

Add the config to run CI on GitHub Actions
Add the config to run CI on GitHub Actions
