A pull request that changes only documentation can be blocked by a required GitHub Actions check even when no test failed. If the workflow never started because its trigger filtered out the change, the required check can stay Pending. A retry cannot help if there is no run to retry.
Find out whether the workflow ran
Open the pull request’s Checks tab and record the name of the required check. Then look for the corresponding workflow run on the pull request’s latest commit. If there is a run, open it and check whether the job is waiting for a runner, waiting for approval, or failing inside a step. If there is no run, inspect the workflow’s trigger and the commit message before changing runner settings.
Check the changed files against the trigger
Suppose an iOS repository ignores changes under docs/** and requires its iOS test workflow before merging. A pull request that edits only docs/setup.md can skip the entire workflow and leave the required check pending. A second request that also changes app code should trigger the workflow if the branch and event filters match. Check the destination branch too. GitHub documents that path filters, branch filters, and commit-message skip instructions can all leave required checks pending.
Keep a required result visible
If the required check must always report a result for relevant pull requests, let the workflow start for those requests. Move the decision about whether to run expensive tests into the workflow. For example, an initial job can classify the change and an always-running final check can report whether tests were skipped intentionally, passed, or failed. Keep the final check name stable and make sure it reports failures from any tests that were required. Avoid wiring branch protection to a job that disappears for docs-only changes.
Verify with three pull requests
Try a docs-only change, an app change with passing tests, and a controlled app change with a failing test. The first should report an intentional skip, the second should run the tests and pass, and the third should still block the merge. If the docs-only request remains pending, compare the exact required check name with the check that the workflow actually reports.
Check the required name against the actual run
Start at the merge box and copy the exact check name that is waiting. Open Actions for the same commit. If there is no workflow run, inspect path and branch filters and the commit message. If there is a run, open it and check whether the job was skipped, failed or completed under a different name. These observations distinguish missing reporting from a test failure.
For example, imagine a repository requires unit-tests, but its workflow only starts when src changes. A documentation-only pull request can leave the required name waiting indefinitely. Re-running an unrelated manual workflow may produce green results without satisfying the pull request requirement. Fix the trigger and required-check design together so the expected result is reported for eligible pull request events.
Test a documentation-only change, a source change with passing tests and a source change with a deliberately failing test in an approved test branch. The first should reach an intentional result, the second should pass and the third must still block merging. Read the check names and commits in each run. Preserve this three-case test when workflow filters change later.
https://docs.github.com/en/actions/how-tos/manage-workflow-runs/skip-workflow-runs