# 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="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2Fd2aLE1jp9nvSw875Q3ip%2FScreen%20Shot%202023-04-20%20at%209.51.52%20AM.png?alt=media&#x26;token=ccae67bd-1354-452d-879c-d74a3020f366" 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="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FG0bNNXoPAiSm9AyBSah6%2FScreen%20Shot%202023-04-20%20at%209.51.07%20AM.png?alt=media&#x26;token=64607846-44d9-4813-bfec-304af6df0019" 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
```