GitHub merge queues
Dagger for Github now supports merge queues. When a pull request joins the queue, Dagger runs your checks on its merge group: the base branch with the pull requests ahead in the queue and this one merged in. The queue merges the group only when the checks pass, so pull requests that pass alone but fail together do not break the branch.
To use it, turn on checks for pull requests in the repository, and add your Dagger checks to the required status checks of the branch that uses the merge queue. You can require each check, or only Run Dagger Checks, which sums up the run. A merge queue waits only for required checks: without them, it merges right away.
The Dagger for GitHub app needs the Merge queues permission to receive merge queue events. If GitHub asks, accept it in the app's installation settings.
Merge group checks get your organization's secrets, because a maintainer queued the pull requests. In Dagger Cloud, a merge queue run has a merge queue badge, which links to the queue and to the pull request that joined the group.