Currently, when Harness CI stages are marked as required checks in GitHub PRs, any stage that is not triggered due to conditional execution or trigger filters does not report a status, causing the PR to remain indefinitely blocked. GitHub supports a “skipped” status for checks, which is treated as a success and does not block merges. We request that Harness report a “skipped” status to GitHub for any CI stage that is intentionally not executed, enabling users to leverage conditional pipeline logic without impacting PR mergeability.