Only post PR comments when Codecov is enabled for the repository
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
The issue names no source files, tests, or entry points. Start by confirming with maintainers which opt-in signal is authoritative—activation, a valid coverage upload, or another repository setting—and define the expected behavior when none exists, including the current comment:false workaround.
Written by the indexing model from the issue text.
Description
Problem
Codecov currently appears to post PR comments on repositories where Codecov isn't actually enabled/configured for the project.
For example, I'm seeing comments like:
⚠️ Please install the Codecov app to ensure uploads and comments are reliably processed by Codecov.
followed by a Codecov report.
This creates unnecessary noise on repositories that aren't intended to use Codecov at all, particularly when Codecov has access at an organization/account level containing multiple unrelated repositories.
Expected behavior
Codecov should only post PR comments when the repository has explicitly opted into Codecov.
For example, a repository could be considered enabled if one or more of the following is true:
- The repository has been activated/configured within Codecov.
- Codecov has received a valid coverage upload for the repository/PR.
- The repository has otherwise explicitly enabled Codecov's PR integration.
If none of those conditions are met, Codecov should not create a PR comment simply asking users to install/configure the Codecov GitHub App.
Current workaround
It looks like comments can be disabled per repository with:
comment: false- Dominant language
- No language data
- Stars
- 52
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from codecov/feedback
-
Docs Waiting for: Product Owner
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Bug ReportOpen
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Docs
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Docs
Difficulty 2/5 1-3 hours Newbie friendliness 20/100