It is now possible to configure pipelines to be triggered specifically when a push to a merge queue occurs.
When a pull request enters GitHub’s merge queue, GitHub creates a temporary branch prefixed with gh-readonly-queue/ that combines the PR’s changes with the latest base branch and any PRs ahead of it in the queue. This is the final validation before code lands on your base branch - and it often calls for a different CI strategy than what you run during code review.
With this trigger, teams using GitHub’s built-in merge queue can run a dedicated workflow at the merge gate - for example, a more comprehensive integration or end-to-end test suite - without slowing down the PR feedback loop. It also makes it straightforward to report a required status check on gh-readonly-queue/* branches, which GitHub needs in order to proceed with the merge.
This trigger option is available to all organizations using GitHub, as long as they have installed the CircleCI GitHub App integration. Access it by adding a new GitHub trigger to a GitHub App pipeline from the Project Settings > Project Setup page.
For more information and a full list of GitHub trigger event options, visit the Docs page.