GitHub coverage uploads skip pushes to branches without pull requests
GitHub Code Quality's upload-code-coverage action now skips coverage uploads on branch pushes without an open pull request instead of failing CI. Uploads resume on the next push after a pull request opens; add a pull_request trigger if coverage should upload as soon as the PR opens.
SessionWatcher editorial · Published · Updated · Source announcement: 2026-10-01
What changes on a new branch
GitHub says the Code Quality upload-code-coverage action no longer fails CI when you push a branch that does not yet have an open pull request. It skips the upload and explains why in an Actions notice and step summary.
This also applies to subsequent pushes until a pull request is opened. Uploads on the default branch and supported pull request events continue to work without changing existing workflow configuration.
Sources: Code coverage uploads no longer fail CI for new branches - GitHub Changelog
How to resume uploads when a pull request opens
If your workflow uploads coverage only on push events, opening a pull request does not itself trigger a new upload. Coverage resumes on the next push to that branch.
To upload as soon as the pull request opens, add a pull_request trigger to the workflow.
Sources: Code coverage uploads no longer fail CI for new branches - GitHub Changelog
Availability
The change is available on GitHub Enterprise Cloud and GitHub Team, including Enterprise Cloud with data residency. GitHub says it is not available on GitHub Enterprise Server.
Sources: Code coverage uploads no longer fail CI for new branches - GitHub Changelog
AI assisted reporting, checked against the linked official sources. Source pages checked 2026-10-01. Editorial process and corrections.