Customer has a merge queue enabled in their GitHub repository, which means that they do not run tests on the default branch. Tests that would otherwise run on the default branch instead run on branches prefixed with gh-readonly-queue/, which means that they have no way to check which tests are preventing PRs from actually merged. An important note in their setup is that they do not block merges on tests that flake on PRs, but they do block in the merge queue. The merge queue is the only gate to merging.

In other words, they still want to see flaky test insights on PR branches but also want to see flaky test insights on any branch prefixed with gh-readonly-queue/.