# Getting Started with MergeQueue

This setup guide will walk you through the initial set up for MergeQueue. Since most capabilities of Aviator revolve around merging, we recommend you to start here. 

1\. Create an account. [<mark style="color:blue;">Register here</mark>](https://app.aviator.co/auth/login).

2\. Follow the onboarding flow to connect to the Aviator GitHub app, authorize one or more repositories that you want to automate.

{% hint style="info" %}
If you have trouble connecting the app, please read the [<mark style="color:blue;">troubleshooting doc</mark>](https://docs.aviator.co/manage/faqs/troubleshooting-github-app-connection).
{% endhint %}

3\. Select the repository on the **Repositories** page to configure the rules. This will take you to the Basic Configuration page to customize some basic settings.

![Configure a repository.](https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FU6oKhEb757Uo1SOgttSV%2FScreen%20Shot%202022-05-23%20at%202.38.56%20PM.png?alt=media\&token=ab671f8a-72bf-4846-a183-d14cf0b25346)

4\. On this page, you will see two GitHub labels. These labels are the most common ways for Aviator MergeQueue to interact with your pull requests. The default trigger label is called **mergequeue**.

![Add a trigger label that tells Aviator your PR is ready to be merged.](https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FRaCEao277bZphCc36Ozg%2FScreen%20Shot%202023-10-12%20at%202.30.13%20PM.png?alt=media\&token=59bf6e76-232b-409e-8611-59fe36e894f9)

5\. Verify the required status checks are set correctly. By default, Aviator sync the required checks from GitHub branch protection rules, but you can customize them here.&#x20;

<figure><img src="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FkdeurXQ9XDPusWWC8xkH%2FScreen%20Shot%202023-10-12%20at%202.32.25%20PM.png?alt=media&#x26;token=d615d953-3400-4c90-9d25-ddc5cb651717" alt=""><figcaption><p>Required checks on Merge Rules page</p></figcaption></figure>

<figure><img src="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FFlh6gN3VHQu4SWOgdZV0%2FScreen%20Shot%202022-12-29%20at%209.14.58%20AM.png?alt=media&#x26;token=19234677-ae92-45ce-ac05-de612a7ab8aa" alt=""><figcaption><p>required check configuration from UI</p></figcaption></figure>

{% hint style="info" %}
If your team is using Parallel mode, Aviator bot will use the same checks for both original PRs and draft PRs. However, if you want to customize checks for draft PRs, you can do so under `Override required checks` in [<mark style="color:blue;">the Parallel Mode section</mark>](https://docs.aviator.co/mergequeue/concepts/parallel-mode).
{% endhint %}

***

That's it. You are ready to go. Now when a PR is ready, tag the PR with the trigger label **mergequeue** defined above. Let the Aviator bot handle the verification and merging the PR.

![Simply add the trigger label and your PR will be queued and merged.](https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FldGYOtvEQXpnj1HMkTUF%2FScreen%20Shot%202022-05-23%20at%205.37.18%20PM.png?alt=media\&token=21a21888-976f-4772-85e0-b375bf0044dc)