Using GitHub's pull request merge queue in your pipelines

GitHub has released Merge Queue, a feature that enhances efficiency and stability of software delivery workflows by automatically handling pull request merges into busy target branches. The merge queue ensures that pull requests are merged in the correct order, reducing CI workloads and potential delivery blockers. Prior to this, developers had to manually merge their pull requests into main, which often led to failed merges due to lack of synchronization with the main branch. GitHub's Merge Queue is available for public repositories owned by an organization or private repositories owned by organizations using GitHub Enterprise Cloud. The feature creates temporary branches to validate pull request changes and only merges them once required checks are satisfied. To get started, developers need to include the gh-readonly-queue/{base_branch}/* filter pattern in their pipeline's settings and enable merge group checkbox in their GitHub repository's webhook configuration.