# Using the Queue

These pages cover the daily operations that developers perform when working with Trunk Merge Queue. Whether you're submitting your first PR or handling a failed test, this section provides practical guidance for getting your code merged safely and efficiently.

### Submit and manage pull requests

[**Submit and cancel pull requests**](/merge-queue/using-the-queue/reference.md)\
How to add PRs to the queue via GitHub comments, CLI, or UI, and remove them when needed.

### Monitor and troubleshoot

[**Monitor queue status**](/merge-queue/using-the-queue/monitor-queue-status.md)\
Track your PR's progress through the queue in real-time via dashboard or CLI.

[**Handle failed pull requests**](/merge-queue/using-the-queue/handle-failed-pull-requests.md)\
Diagnose failures, retry flaky tests, fix issues, and resubmit.

### Emergency procedures

[**Emergency pull requests**](#emergency-procedures)\
Bypass the queue for critical production fixes (use sparingly).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.trunk.io/merge-queue/using-the-queue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.