codecov / codecov/codecov-browser-extension

[BUG] Not working on improved pull request "Files Changed" experience

Open
#154 4 comments 6 reactions 1 assignee View on GitHub

@spalmurray is already working on this.

Since Jan 6, 2026.

bug
Dominant language
TypeScript
Stars
47
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
Github is testing an improved pull request "Files Changed" experience for which there are several prompts on the page to encourage usage:

above the diff viewer:
Image

and top right:
Image

This changes the URL structure to end in /changes instead of /files, which causes extension 0.7.0 to print the following in the console, and as a result, not modify the page display at all:

☂️ codecov: PR not detected at current URL

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://github.com/codecov/umbrella/pull/633/changes
  2. Click on "Try the new experience" if redirected to the old experience
  3. Check the browser console
  4. See error

Expected behavior
Coverage is displayed as it is in the old experience

Regression
Unsure, as I'm a new user of the extension, but @spalmurray seems to have added support for a new PR experience in https://github.com/codecov/codecov-browser-extension/pull/152 but perhaps that was a different experiment

Product Area
browser ext

Versions

  • OS: macOS 26.2
  • Git Host: Github
  • CI/CD: CircleCI
  • Uploader: codecov-circleci-orb@v5
  • Browser: Firefox 146.0.1
  • Extension: 0.7.0

Additional context
This template should probably be updated for this repo to ask for more relevant info to the browser ext, rather than the CodeCov service itself. I've added additional versions like Browser/Extension that seem relevant here.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.