PR comment missing project coverage for open source repo
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github, yaml
- Domain
- ci-cd, testing-qa
Research direction
Start by reviewing the supplied Codecov comment configuration and comparing the reported PR output with the project and Codecov pages linked in the issue. Check the discussion in #802 for the expected open-source PR comment layout; done means identifying why project coverage is omitted and documenting the configuration or account/project setting that restores it.
Written by the indexing model from the issue text.
Description
Hi,
I've recently setup codecov on a public repo. The integration, components and reported coverage are correct. However, I'm having troubles tweaking the PR commen
Similarely to #802 i only get something like
Additionally on the codecov repo's page i get
While I'm on a developer plan. The pricing list mention that coverage flags & components are available for open source projects. Apparently as mentionned in #802 this also includes the PR comment layout.
I think that the issue may arise from the fact that some of the organisation repositories are private.
How can i register that the project is open source & public. Or fix the comment.
PS: the YAML has been validated and the current PR comment config is:
comment:
layout: "reach,diff,flags,files,footer"
behavior: new
require_changes: false # learn more in the Requiring Changes section below
require_base: false # [true :: must have a base report to post]
require_head: true # [true :: must have a head report to post]
hide_project_coverage: false # [true :: only show coverage on the git diff]
Project github page: https://github.com/Shamrock-code/Shamrock
Codecov page : https://app.codecov.io/github/Shamrock-code/Shamrock
- Dominant language
- No language data
- Stars
- 52
- Forks
- 25
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Bundle analysis: `normalizePath` replaces everything after the first `-` in a file name, so different assets collidePossibly taken @ChiptenIsCool claimed this 16 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Docs Waiting for: Product Owner
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 1-2 days Newbie friendliness 42/100
All issues in codecov/feedback
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nutmos/expensetrackr#157 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
janitor-team/janitor#2613 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
keyxmakerx/Chronicle#2550 ·
Maintainers usually reply within 1 day
-
ci/cd javascript medium sdk
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug good first issue help wanted rust type:infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Open-Glassbeetle/glassbeetle#374 ·
Maintainers usually reply within 1 day