Re running PR checks when changes to ruleset workflow is made

[chopkinsmade]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

General

Discussion Details

We use Organisation rulesets and the Require workflows to pass before merging option to define common checks we want all repositories to run when raising a PR into main.

These common checks are running when a PR is raised on any repository in the organisation, and reporting the status on the PR, for example:

The required workflow in the ruleset is configured to use the main branch in our central repo where we store our github action yml files. This has worked up until this point, however we want to start using release tags to avoiding all repositories in the organisation using the main branch.

We've added a job in our release GitHub action that uses the gh api to update the rulesets to use whatever tag the latest version is, and this works as expected. However, when the ruleset is updated to use the latest tag, all the open PRs that had a successful common check are now marked as Expected — Waiting for workflow to run.

This job remains in the waiting status, and is never started. It makes sense that a change to the branch used by the ruleset requires the workflow to be rerun, but I would expect that to happen automatically. As that isn't happening here, are there any API endpoints that can re-trigger the workflow. We can force the jobs to rerun by either pushing an empty commit, or closing and reopening the PR but as we have these checks across multiple repositories that isn't feasible