# Require an Aviator Status Check

Aviator provides a [<mark style="color:blue;">GitHub status check</mark>](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) that you can enable for your PRs. You can also add this status check as a required check in [<mark style="color:blue;">branch protection rules</mark>](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule) to prevent developers from bypassing the merge queue. In the branch protection settings, you can find this check with the name: `aviator/checks`.

<figure><img src="/files/i3HwajkJ4FFA8DOKvWaK" alt=""><figcaption><p>aviator/checks as a GitHub status check</p></figcaption></figure>

The check typically contains similar details that you also see on the sticky comment.

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

This check is enabled by default but it can be disabled using the config setting below:

```
merge_rules:
  publish_status_check: false
```


---

# 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.aviator.co/mergequeue/how-to-guides/require-an-aviator-status-check.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.