# Merge Queues

PullApprove works with [GitHub merge queues](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue) without any configuration in `CODEREVIEW.toml`.

When a pull request is added to the queue, GitHub builds a temporary `gh-readonly-queue/...` branch and asks every required check to report on it again. PullApprove's review requirements were already enforced on the pull request itself before it could be queued, so there is nothing new to evaluate. PullApprove posts a passing status on the queue branch with the description "PRs already evaluated" and the queue continues.

![Commit checks on a merge queue commit showing the PullApprove status as "PRs already evaluated"](/assets/docs/img/merge-queue-checks.10005f5.png)

This means a queued pull request is never blocked waiting on PullApprove, and the PullApprove status is still required on the merge commit that lands on the protected branch.