Overview of the GitHub Code Quality Update

Code coverage uploads from the GitHub Code Quality upload-code-coverage action no longer fail CI when developers push a branch that does not yet feature an open pull request. According to the official [GitHub Changelog](https://github.blog/changelog/2026-10-01-code-coverage-uploads-no-longer-fail-ci-for-new-branches/), this refinement improves the continuous integration experience by eliminating unnecessary friction during the early stages of feature development.

Under the previous system, the coverage API strictly required a pull request number for any push directed to a non-default branch. Because that particular number only becomes available once an official pull request is opened, pushing a fresh branch ahead of time routinely forced the coverage-upload step to fail, despite there being no underlying issues with the developer workflow.

How the Updated Action Handles Unassociated Branches

With the new behavior in place, when the action executes on a push to a branch that lacks an associated pull request, it gracefully skips the upload process instead of triggering a failure. It then explicitly clarifies why the action was skipped inside an Actions notice and step summary.

This operational change covers initial pushes to branches that do not yet have an open pull request, as well as any subsequent pushes to those specific branches until a pull request is formally opened. Meanwhile, uploads for pushes targeting your default branch, along with supported pull request events, continue to operate precisely as before, meaning teams do not need to modify any existing workflow configurations.

Workflow Triggers and Pull Request Behavior

If a workflow is configured to upload coverage exclusively on push events, opening a pull request will not automatically trigger a brand new upload on its own. Instead, coverage data collection resumes naturally on the very next push to that particular branch.

Teams wishing to capture coverage data the exact moment a pull request opens can easily adjust their setup by incorporating a pull_request trigger directly into their workflow. Developers seeking detailed configuration steps can consult official documentation on [setting up code coverage for your repository](https://docs.github.code-security/how-tos/maintain-quality-code/set-up-code-coverage) for further guidance.

Platform Availability and Deployment Scope

This functional improvement is currently live and available across GitHub Enterprise Cloud and GitHub Team environments, which explicitly includes GitHub Enterprise Cloud deployments utilizing data residency features. However, it is important to note that this specific update is not available on GitHub Enterprise Server instances.

Users looking to explore additional updates, historical releases, or return to the main announcements can easily navigate back using the [Back to changelog](https://github.blog/changelog/) link provided by the platform.

Sources

• GitHub ChangelogCode coverage uploads no longer fail CI for new branches