Title: Enable “required status checks” for pull requests
Author: WordPress VIP Documentation
Published: February 2, 2022
Last modified: February 3, 2026

---

 1. [Code deployment](https://docs.wpvip.com/code-deployment/)
 2. [GitHub repository](https://docs.wpvip.com/code-deployment/github-repository/)
 3. Enable “required status checks” for pull requests

#  Enable “required status checks” for pull requests

Enabling [GitHub’s required status checks for branch protection](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-status-checks-before-merging)
ensures that no pull requests are merged unless they are free of issues, automatically
detected by the [VIP Code Analysis Bot](https://docs.wpvip.com/vip-code-analysis-bot/)(
the Bot). This enforces a workflow where pull requests require developers to get
clearance from the VIP Code Analysis Bot before they can merge the code.

**Prerequisite**

Users must have [access to an application’s GitHub repository](https://docs.wpvip.com/manage-user-access/)
with a [GitHub admin role](https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)
for that repository in order to manage branch protection rules.

To enforce VIP Code Analysis Bot review, create a [branch protection rule](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)
in GitHub and specify the `VIP Code Analysis Bot` [commit status context](https://docs.github.com/en/rest/reference/commits#commit-statuses):

 1. Navigate to an application’s GitHub repository. This URL can be found in [the application’s VIP Dashboard](https://docs.wpvip.com/vip-dashboard/dashboard/).
 2. Under the repository name, select the **Settings** tab.
 3. In the “Code and automation” section of the sidebar, select** Branches**.
 4. Next to “Branch protection rules”, select **Add rule.**
 5. In the field below “Branch name pattern”, type the branch name or pattern to protect.
 6. Under “Protect matching branches”, enable “**Require status checks to pass before
    merging**“.
 7. _(Optional but recommended)_ Enable “**Require branches to be up to date before
    merging**“. This ensures pull requests targeting a matching branch have been tested
    with the most recent code.
 8. In the search field, search for “**VIP Code Analysis Bot**” and select it in the
    results provided. This option will not be available if the Bot has not interacted
    with the repo in the past 7 days. This can be remedied by creating a or modifying
    an existing pull request.

[[

Screen shot of the **VIP Code Analysis Bot** option in the status checks dropdown

 9.  Select the “**Create**” button.

## Deactivated merge button

Branch protection rules can [cause the merge button on a pull request to remain deactivated](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#required-reviews)
until all reviews pass or are dismissed. This can occur if previous reviews from
the VIP Code Analysis Bot or another reviewer have not yet been addressed. It is
also possible for a user with write access to the repository to [dismiss the blocking review](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review).

**Note**

By default, the VIP Code Analysis Bot is disabled for pull requests that are created
by Codebase Manager from within [the VIP Dashboard Plugins panel](https://docs.wpvip.com/codebase-manager/plugins-panel/).
Pull requests created by Codebase Manager will not be analyzed by the VIP Code Analysis
Bot even in branches with a required status check enabled. Because of this conflict,
the “Merge” button will not appear as expected. Only a user with a GitHub admin 
role can bypass the branch restrictions and merge the pull request.

Last updated: February 03, 2026