Possibility to run the cri-o/kata CI job on PRs for this repository?

[littlejawa]

We have a CI job running on cri-o repository, testing the cri-o PRs against kata's main branch (http://jenkins.katacontainers.io/job/kata-containers-2-crio-PR/).

This job is running scripts hosted in this (kata-containers/tests) repository.

This job is not triggered on PRs for this repository, so whenever we change these scripts, the CI doesn't test them. We have to merge the change and then trigger a build on the cri-o side to see if we broke something.

There is not a lot of changes to these scripts, so I'm not sure it's worth running the job on every PR for the tests repo. On the other hand, merging blindly feels bad, and I would feel much safer if the CI could tell me when my PR breaks something before it goes upstream.

I am not familiar with github automation : how can we make such changes tested before being merged? Should we enable it on all PRs? Can we have it triggered for specific file changes, or only manually triggered when needed?

I'm willing to set it up - not pushing the work on someone else - but I genuinely don't know what the proper solution is.