In project A we push changes daily to branches that actions build and run regression tests on automatically. The regression tests currently run in sequence in the same workflow, but as a separate step, on virtual hardware (Qemu) and now we want to trigger tests on actual hardware as well.

We had this idea about creating a project A-hardware-test template that we (and others) can fork for each hardware test system we build. Hence we cannot rely on repository_dispatch in A to trigger workflows in A-hardware-test instances. Is there a way of achieving this without polling (cron)?

Ideally, A-hardware-test instance should also be able to report to an PR that it’s picking up jobs and have finished them.

Additional info: the build step use actions/upload-artifact@v4 so we had this idea about triggering on workflow A run id and artifact availability? That way the hardware tests could start almost at the same time as the virtual tests run (since v4 artifacts are available before the run has completed.)