codecov/project status has never arrived on any commit; every commit is recorded on branch main despite --branch
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
- Active
- Tech stack
- github-actions, python
- Domain
- ci-cd, testing-qa
Research direction
Start with .github/workflows/ci.yml and codecov.yml, then compare the codecov-action@v7 uploader logs with the commit uploads and status responses for pull request heads. Reproduce using the existing pytest --cov workflow and inspect whether branch recording and project-status generation share a cause. Done means the missing project status and main-branch recording are explained and the appropriate behavior is verified.
Written by the indexing model from the issue text.
Description
Repository: github.com/evkir/CyberAI (public, free tier, GitHub Actions)
What is expected
codecov/project posted as a status on pull request head commits, alongside codecov/patch.
What happens
codecov/patch arrives and succeeds. codecov/project has never arrived on any commit since the repository was connected. Separately, every commit is recorded with branch: main, including pull request heads, although --branch is sent.
Latest example, merge commit 6280d8a7e7a70bbf9dfda9a97962f323308dc1fb: nine GitHub check-runs all successful, combined status carries exactly one entry, codecov/patch success. No codecov/project in either list.
This is not a regression. Across the head commits of pull requests 258 to 267, patch appears from 261 onwards and project appears on none of the ten.
What has been ruled out, and how
-
Configuration. The effective Repository YAML shown in the Codecov UI contains
coverage.status.project.defaultwithtarget: auto,threshold: 0.5,if_ci_failed: error.codecov.ymlin the repository validates against the validation endpoint. -
Delivery channel.
codecov/patchis delivered on the same channel and arrives, so notifications reach GitHub. -
What the client sends. The uploader log shows
--prand--branchwith the correct values.override_prandoverride_branchare set from the event payload. -
A base to compare against. The pull request object carries both
base_totalsandhead_totals. The base branchmainhas a report. -
Checkout depth. Raised to
fetch-depth: 0and the next commit still hadpatchand noproject. -
Authentication method. This was run as a separating experiment. The upload ran under a repository
CODECOV_TOKENfor one day, and under OIDC (use_oidc: true) before and after. Under the token, on head36d6f0a2ea75fbd83669b4c8d9d450c4ad391497:patchsuccess, commit still recorded onbranch: main,projectabsent. Under OIDC, on6280d8a: identical outcome. The authentication method changes neither the recorded branch nor the missing status. -
Uploads arriving at all.
GET /api/v2/github/evkir/repos/CyberAI/commits/{sha}/uploads/returnscount: 4with four results on each of36d6f0a,4157df8and6280d8a, every one namedCyberAI CI - test, providergithub-actions, statemerged, flags empty. The version matrix has four entries, so every upload sent is stored.
Questions
- Why is a pull request head commit recorded on
branch: mainwhen--branchnames the head branch? - What causes
codecov/projectto be withheld whilecodecov/patchis computed and posted from the same commit? - Are the two the same cause?
Environment
codecov/codecov-action@v7, GitHub Actions, Python matrix 3.11-3.14, one upload step with no condition, coverage produced by pytest --cov --cov-report=xml. Workflow: https://github.com/evkir/CyberAI/blob/main/.github/workflows/ci.yml
- 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