MMTk core uses workflow dispatch to trigger binding tests

[qinsoon]

[qinsoon]

I don't think workflow_dispatch would work here. We would want to dispatch a workflow run from a mmtk-core PR to a binding PR. However, both the mmtk-core PR and the binding PR may be from a fork. If we would like to run a workflow with workflow_dispatch in a fork-origin PR, we need a token that has write access to the fork repo, which we don't have. Our secrets do not have write access to an arbitrary fork repo, and the GITHUB_TOKEN with the pull request (in mmtk-core) can only access mmtk-core, not other repos.

The closest solutions that may work are:

• Do workflow_dispatch after PRs are merged. We can dispatch to run tests after both the mmtk-core PR and the binding PR are merged, in which case, we just need a token with write access to mmtk/ repos.
• Do workflow_dispatch to base repo. We can dispatch to the workflow in the binding base repo (under the mmtk/ org). In the workflow, we can check out PR code from a public fork. But in this case, if the PR also changes the workflow, it still executes the old workflow from the base repo.

The first might be acceptable, if we are happy to run tests after the PRs are merged. The second does not sound better than what we have right now (running scripts from the binding repos).

However, either sounds perfect for now. I probably will stop investing more time into this, and we will still use scripts to run binding tests. I will keep this issue open for a while. If you have a better idea, just let me know.