[sdf-jkl]

Summary

Fix premature merge-queue merges introduced by #11788.

The broadened push trigger also matches GitHub-managed gh-readonly-queue/** branches. A queue commit therefore triggers both push and merge_group runs of the CI workflow. The upstream queue-branch push run skips Required Checks, potentially satisfying the required status prematurely while the full merge_group run is still pending.

It's actually in DataFusion too, but I missed it 🤦

Fix

• Exclude gh-readonly-queue/** from push-triggered CI while keeping fork branch pushes enabled.
• Update the CI configuration validation test to enforce this exclusion.
• Keep merge_group CI unchanged.

Evidence

• fix(arrow-select): include column name in BatchCoalescer errors #11870 merged at 07:18:57 UTC on October 24, while its full merge-group CI finished at 07:35:36 UTC.
• The corresponding queue-branch push run was skipped.
• All 11 merges audited after Run fork PR test suites in contributor forks #11788 merged before full merge-group CI finished, and each had a skipped queue-branch push run.

Validation

Static workflow config/assertion updated. The behavior still needs validation with an actual merge-queue PR. Keep this as draft until verified.

[sdf-jkl]

@alamb @Jefffrey

[alamb]

It's actually in DataFusion too, but I missed it 🤦

As in Datafusion PRs bypass the queue? I have seen several PRs that got rejected by tests in the queue, so I am not sure about this

[alamb]

let's try it

[alamb]

Thank you @sdf-jkl

[sdf-jkl]

As in DataFusion added an exception for gh-readonly-queue/**

Datafusion is fine 🫡

[Jefffrey]

thanks for this ❤️