Problem
Currently, Native Deployment Checks (lint and typecheck) allow selecting which environments they run on (Preview, Production, or both). However, GitHub Checks don’t have this option and only run on Production deployments.
This limits teams that need to validate deployments with custom scripts across different environments.
Current Behavior
- Native Deployment Checks →
Environment selection available - GitHub Checks →
No environment selection (Production only)
Proposed Solution
Add an environment selector to the GitHub Checks configuration in Project Settings → Deployment Checks.
Use Case
Our team runs custom validation scripts via GitHub Actions. We need these checks to run on Preview deployments to:
- Catch issues earlier in the development workflow
- Validate feature branches before merging
- Maintain consistent validation across all environments
Current Workaround
Using Native Deployment Checks, but these are limited to lint and typecheck only. There’s no way to run custom scripts with environment selection.