Static Checks, Dynamic Pull Requests: GitHub's Merge Validation Gap

GitHub's required checks are static policies that don't adapt to the nature of each pull request—forcing documentation-only changes to wait for backend builds and security scans that never apply. This architectural mismatch forces teams into bad choices: waste CI resources on irrelevant checks, weaken protection by requiring fewer checks, or embed policy logic inside workflows. The real solution is separating execution policy from merge requirements, enabling different PRs to enforce different checks based on actual changes.