---
title: Queue
description: Put your pull request into the merge queue.
---

The `queue` action allows you to put a pull request into the [merge
queue](/merge-queue). By placing pull requests in the queue, you can make sure
they are up-to-date and control their processing based on their priority.

If your queue rule has [`autoqueue:
true`](/merge-queue/rules#autoqueueing-pull-requests), matching pull requests
are added automatically and you usually do not need this action. Use the action
when you want explicit, rule‑driven or conditional enqueueing beyond what
`queue_conditions` express.

## Parameters

| Key name | Value type | Default | Description |
| --- | --- | --- | --- |
| `name` | string or null | `null` | The name of the queue rule where the pull request should be added. If no name is set, queue_conditions will be applied instead. |

## Examples

```yaml
pull_request_rules:
  - name: put PRs in queue
    conditions:
      - label = queue-me
    actions:
      queue:
```

In this example, any pull request that has the label `queue-me` will be
automatically queued. The pull request still needs to match the
`queue_conditions` defined in the queue to enter the queue.

:::note
  By default, Mergify injects your GitHub branch protections and ruleset
  rules as queue conditions. If some ruleset rules are incompatible with
  your queue setup, see [GitHub Rulesets
  Compatibility](/merge-queue/github-rulesets) for resolution steps.
:::