E2E tests skipped for GitHub merge queue events
Merge queue events no longer trigger end-to-end test suites, cutting CI noise and compute waste when rebasing in GitHub's merge queue.
GitHub's merge queue can rebase and validate pull requests automatically before merging. Each of these validation runs previously fired the full E2E test suite, even though the underlying code hadn't changed—only its position in the branch hierarchy had.
A single-line condition update now prevents the E2E tests from running when github.event_name is merge_group. The job still runs for normal PR pushes and when the ci or e2e build outputs are set, but merge group events are explicitly excluded.
This keeps merge queues fast and focused. CI resources go toward testing actual code changes rather than validating that GitHub can rebase correctly.
View Original GitHub Description
Summary
Prevents the e2e-tests job from running when a pull request is processed by a GitHub merge queue.
Related Linear tickets, Github issues, and Community forum posts
Review / Merge checklist
- PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
- Docs updated or follow-up ticket created.
- Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
- PR Labeled with
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)