Required or no-op status check missing after enabling the GitHub App

Overview

After enabling the GitHub App integration (or migrating a project from the legacy GitHub OAuth connection), a required status check (often a no-op gate or approval job) may appear to stop reporting to GitHub. Pull requests then stay blocked because the required check never arrives.

The check is still being sent. On GitHub App pipelines its name changed: it no longer includes the workflow-name prefix.

Status check naming on GitHub App pipelines

On projects triggered by the GitHub App, all job types use the same format: the job name only.

This differs from the GitHub OAuth connection, where approval, no-op, and release jobs use ci/circleci: <workflow_name>/<job_name>. See Why Status Updates for Approval, No-Op Jobs and release Include Workflow Names.

Solution

1. Open the commit or PR and note the actual check name CircleCI now posts (e.g. ci/circleci: required).
2. In GitHub, go to Settings → Branches → Branch protection rules for the affected branch.
3. Update the required status check from ci/circleci: <workflow_name>/<job_name> to ci/circleci: <job_name>.
4. Re-run a pipeline on an open PR and confirm the check appears and satisfies the rule.

Additional Resources

• Why Status Updates for Approval, No-Op Jobs and release Include Workflow Names: the OAuth naming rules
• Simplify GitHub required status checks with no-op jobs
• Status updates overview