Skip to main content
When using Plan and Apply via PR Comments, env zero checks that a pull request is mergeable before running an apply. If you also set the env0/Apply commit status as a required status check in GitHub branch protection, this creates a circular dependency: the PR is not mergeable because env0/Apply has not passed yet, but apply cannot run because the PR is not mergeable. The Bypass Apply Mergeability Check policy resolves this by evaluating the PR’s mergeability while excluding env zero’s own Apply status checks from the requirements.
This policy applies to GitHub and GitHub Enterprise only. Other VCS providers are not affected.

​
How It Works

When this policy is enabled, env zero evaluates the PR’s mergeability by querying GitHub’s branch protection rules and repository rulesets directly, rather than relying on GitHub’s merged mergeability state. During this evaluation, env zero excludes its own Apply-related status checks (such as env0/Apply) from the required checks list. This means all other branch protection requirements (such as required reviews and other CI checks) are still enforced. Only the env zero Apply checks are bypassed.

​
Enabling the Policy

Navigate to Organization Settings → Policies, and under Plan and Apply from PR comments, check Bypass PR mergeability check for env0/Apply (GitHub only).

​
When to Use This Policy

Enable this policy if you:
  1. Use PR comment applies
  2. Have GitHub branch protection or repository rulesets that require the env0/Apply status check to pass before merging
If you do not have env0/Apply set as a required status check in your GitHub branch protection rules, you do not need this policy.