> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/mergequeue/how-to-guides/set-up-pre-queue-conditions.md).

# How to Set Up Pre-Queue Conditions

This guide describes how to setup [<mark style="color:blue;">pre-queue conditions</mark>](/mergequeue/concepts/pre-queue-conditions.md).

## RegExp PR Title and Body Validation

Aviator supports validating the PR title and description. For instance, if you want to require each PR title to have a ticket number, or if you have a checklist of items in the body, you can setup the preconditions:

```yaml
preconditions:
  validations:
   - name: Require JIRA ticket in title
     match:
       type: title
       regex:
       - '^\[AVT\-\d+\].+$'
   - name: Require tests have been run checkbox
      match:
        type: body
        regex:
        - '^\[x\] All relevant tests have been run$'
    - name: Require documentation checkbox
      match:
        type: body
        regex:
        - '^\[x\] The documentation has been updated$'
```

Using this now, Aviator will look for a PR title starting with “\[AVT-”, and would require the body to have the following two checks marked as done:

```
[x] All relevant tests have been run
[x] The documentation has been updated
```

<figure><img src="/files/CkrSQ2kZcHzwjHcmgs1P" alt=""><figcaption></figcaption></figure>

When the checks fail, you will see the “name” of the validation reported in the comment as failure, blocking the PR from getting queued:

<figure><img src="/files/aUAQcIEQITJzGyt07Lp5" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.aviator.co/mergequeue/how-to-guides/set-up-pre-queue-conditions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.