Problem
schema-parity and verify-non-root are path-filtered workflows (run only on DB-schema / Docker-surface changes) that were added to dev's required status checks. On any PR that doesn't touch those paths the required context never reports, so GitHub holds the merge at "Expected — waiting for status" indefinitely.
Impact: every non-schema / non-docker PR was unmergeable. The approved queue (#1078, #1168, #1213, #1166, #1195, #1202) had to be unblocked by temporarily dropping both checks from required branch protection. schema-parity.yml even carried a maintainer note predicting this exact failure.
Fix
Convert both workflows to always-run + self-skip: the job runs on every PR and a pure git diff detector gates the heavy steps. No relevant change → heavy steps skipped → job passes trivially (required check satisfied). Relevant change → full check runs and can fail. No third-party action, no token scope beyond contents: read.
Acceptance
Problem
schema-parityandverify-non-rootare path-filtered workflows (run only on DB-schema / Docker-surface changes) that were added todev's required status checks. On any PR that doesn't touch those paths the required context never reports, so GitHub holds the merge at "Expected — waiting for status" indefinitely.Impact: every non-schema / non-docker PR was unmergeable. The approved queue (#1078, #1168, #1213, #1166, #1195, #1202) had to be unblocked by temporarily dropping both checks from required branch protection.
schema-parity.ymleven carried a maintainer note predicting this exact failure.Fix
Convert both workflows to always-run + self-skip: the job runs on every PR and a pure
git diffdetector gates the heavy steps. No relevant change → heavy steps skipped → job passes trivially (required check satisfied). Relevant change → full check runs and can fail. No third-party action, no token scope beyondcontents: read.Acceptance
schema-parity+verify-non-roottodevrequired checks