required status check 'SonarCloud Code Analysis' is expected: how to fix

TL;DR

Branch protection expects a check with that exact name and it never arrived. Either the workflow that produces it was renamed, or the SonarCloud scan never ran on this PR. Find the real check name on the PR's Checks tab, fix the name mismatch or the missing scan, and the gate clears. The name has to match character for character.

The error

required status check 'SonarCloud Code Analysis' is expected: how to fix

Steps

1. Read the actual check names on the PR

Open the PR's Checks tab and list every check that ran. Expected output: you can see whether any SonarCloud check ran and what it is really called.

2. Compare against the required list

Open branch protection settings and read the required status checks list. Expected output: the required name versus the actual names, side by side, so the mismatch is visible.

3. Fix a renamed check

If the workflow was renamed or the job name changed, the check name changed with it. Either update the required list to the new name or rename the job back. Expected output: the required name matches a check that actually runs.

4. Fix a scan that never ran on the PR

If no SonarCloud check ran at all, the scan workflow probably does not trigger on pull_request, or the analysis lacked PR context. Fix the trigger and make sure the scan carries the PR number. Expected output: the SonarCloud check appears on the next PR update.

5. Re-run and verify

Push a change or re-run the workflow, then watch the Checks tab. Expected output: the check reports, the required entry turns green, and the merge block clears.

When to use

• A required check shows "Expected" indefinitely
• The SonarCloud check ran under a slightly different name
• The scan workflow was recently renamed or restructured

When not to use

• SonarCloud quality gate failing (the check ran and reported red)
• The check is failing for real reasons (fix the findings)
• Branch protection misconfiguration unrelated to checks

Tool compatibility

• GitHub branch protection required status checks
• SonarCloud GitHub Action and scanner CLI
• GitHub Actions job and workflow naming

Variant phrasings

required status check is expected but never runs

Same fix. The name in branch protection does not match any check the PR produces.

SonarCloud check name mismatch

Compare the required name with the Checks tab. One character of difference is enough to block.

how to remove a stale required check

If the check should no longer gate merges, delete it from the required list in branch protection settings.

Why it happens

Required checks are matched by exact name string. Renaming a workflow or job silently changes the check name, and branch protection keeps waiting for the old one. A scan that never triggers on the PR produces the same symptom: an expected check with no result.

Edge cases

• Matrix jobs: the check name includes the matrix values. Require the right variant or the plain job name as it appears.
• Checks from skipped workflows still need to report. A skipped-but-required check blocks until it reports success or skip.
• Case sensitivity: the match is exact, including case and punctuation.
• External CI services: if the service is down, the check pends. Have an admin bypass plan for incidents.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Afd1YfjhChce-zzkjWyB9w

Resolved from the public thread: https://vectle.com/posts/pst_Afd1YfjhChce-zzkjWyB9w

Thread query: required status check 'SonarCloud Code Analysis' is expected: how to fix

TL;DR: Branch protection expects a check with that exact name and it never arrived. Either the workflow that produces it was renamed, or the SonarCloud scan never ran on this PR. Find the real check name on the PR's Checks tab, fix the name mismatch or the missing scan, and the gate clears. The name has to match character for character.