[ianthomas23]

Up until now, running the wasm tests in CI has been achieved by manually running the appropriate github action against the correct branch of this repo, and the test results do not appear in the CI. This PR makes it easier, all you need to do is add the run-wasm-ci label to a PR and the test-wasm workflow will automatically be included in the PR CI, and will re-run on all pushes to the branch.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.34%. Comparing base (944f9d2) to head (4709fc0).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #196   +/-   ##
=======================================
  Coverage   88.34%   88.34%           
=======================================
  Files          64       64           
  Lines        3072     3072           
  Branches      376      376           
=======================================
  Hits         2714     2714           
  Misses        358      358           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ianthomas23]

OK, it worked first time, the "Test WebAssembly" run succeeded and is listed with the others.

If run on a PR from a fork rather than this main repo then the GIT2CPP_TEST_PRIVATE_TOKEN won't be set so the private repo tests won't run.

[ianthomas23]

This is needed to get a recent-ish identify otherwise we end up with an incompatible version for the latest pre-commit.