Skip to main content
When Plan on Pull Request is enabled, for every commit of a Pull Request, we report a commit status check based on the status of the associated PR Plan that ran in env zero. See Plan on Pull Request for more info on commit statuses. By default, if there was a PR commit that didnโ€™t include any changes that are relevant to the env zero environment, because the commit doesnโ€™t include changes in a file that is part of the glob pattern or template directory, then env zero reports the commit as status โ€œskippedโ€ in GitHub, or โ€œsuccessโ€ in other VCS-es. Marking the commit as โ€œskippedโ€ allows you to set those status checks as โ€œrequiredโ€ in your VCS.
However, for some use-cases you might want env zero not to set those status checks as โ€œskippedโ€. For example, if you have a lot of env zero status checks on your PR that you donโ€™t want to see there.
For that, we have the โ€œDo not report skipped status checksโ€ policy. When setting it, env zero will not create the status checks at all, instead of marking them as โ€œskippedโ€. Setting the policy could be very helpful for a monorepo setup that includes many Templates, for example.
Required Status CheckIf you want to make an env zero status check be required in your VCS - you canโ€™t use this policy. If a PR Plan is not run and this policy is checked, then we wonโ€™t create a status check at all, and merge will be blocked
Configure this policy in Organization Settings -> POLICIES Setting this policy can help avoid the following situation in your pull requests:
Pull request status checks display

Pull Request status checks

โŒ˜I