Setup common workflows for all GH repositories (public/private)

[CMCDragonkai]

Description

We can reuse workflows defined here for all repos to avoid having to do so much repeat work when we are working on the workflows.

Issues Fixed

• Fixes https://github.com/MatrixAI/Orchestrator/issues/43

Tasks

• 1. Setup workflows for library JS repos
• 2. Setup workflows for native library JS repos
• 3. Setup workflows for website apps
• 4. Setup worfkflows for desktop/CLI apps

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build

[CMCDragonkai]

@brynblack @tegefaulkes

[CMCDragonkai]

This is going to work for repositories that have the new lint.mjs script, that way we only need to do npm run lint for things to work.

[CMCDragonkai]

So something I found is that the cobertura report is no longer properly generated. Actually coverage reports all just empty now. I actually don't remember when this was regressed on. It's possible that it has to do with the ESM changeover... right now not that important so skipping fixing this.

[CMCDragonkai]

So the check test job should look like this:

  check-test:
    name: "Check / Test"
    runs-on: ubuntu-latest
    container:
      image: ghcr.io/matrixai/github-runner
    steps:
      - uses: actions/checkout@v4
      - name: Run tests
        run: |
          nix develop .#ci --command bash -c $'
          npm run test -- --ci --coverage
          '
      - name: Upload JUnit report
        if: success() || failure()
        uses: actions/upload-artifact@v4
        with:
          name: junit-report
          path: tmp/junit/junit.xml
      - name: Publish JUnit Report
        uses: mikepenz/action-junit-report@v5
        with:
          report_paths: tmp/junit/junit.xml
      - name: Upload Cobertura report
        if: success() || failure()
        uses: actions/upload-artifact@v4
        with:
          name: coverage-report
          path: tmp/coverage/cobertura-coverage.xml

Here we can see we needed to add the if: success() || failure() to ensure that the subsequent jobs run even if the test fails which is important for junit reports and coverage reports.

I also added the JUnit report processor as we no longer have that automatic like in gitlab.

[CMCDragonkai]

So I have 3 jobs in the feature branch for library JS repos:

• check-lint
• check-test
• check-build

The check-build is a "feature" job that runs to sanity check that the build works.

However we don't keep around the artifact do we? I guess it would depend on what is being built. That would be a the dist directory for library code. Whereas for the SSG websites that's the public directory.

[CMCDragonkai]

Ok so I've got library-js-feature.yml in .github. I want to test this for now to see if I have it properly setup. I want to test it in js-contexts under the feature-ci branch.

We will see if it we can reference it properly.