GitHub Code Coverage Uploads No Longer Fail CI for New Branches
The GitHub Code Quality upload-code-coverage action now skips and explains coverage uploads for new branches without a pull request instead of failing CI. This improves workflow reliability for developers pushing new branches.
What changed?
The GitHub Code Quality upload-code-coverage action no longer fails CI when uploading code coverage for pushes to branches that do not yet have an open pull request. Previously, pushes to non-default branches without an associated pull request caused the coverage upload step to fail, even though workflow configuration was not incorrect. Now, the action skips the upload in these cases and reports the reason via a step summary and Actions notice. This update is available for GitHub Enterprise Cloud and GitHub Team (including data residency), but not for GitHub Enterprise Server.
Why does it matter to an everyday developer?
This improvement means developers will no longer encounter unnecessary failed CI runs just for pushing a new branch before opening a pull request. Routine development flows—where new branches are pushed before their PRs are created—will now have cleaner CI logs and avoid confusion around seemingly broken workflows. CI failures are now more likely to reflect real issues, not internal coverage upload limitations.
What can the developer do now?
No changes are required for existing workflow configurations. Code coverage uploads for pushes to the default branch and supported PR events will continue as before. If you want coverage uploads to trigger when a pull request is opened, add a pull_request trigger to your workflow. For most users, this update simplifies branch management by automatically handling a common edge case.
