MacHu-GWU/sqlalchemy_upsert_kit-project / .claude/skills/pywf-oss-base
pywf-oss-base
FlaggedShared conventions, references, and scripts of the pywf-oss skills for pywf open-source Python libraries: setup, layout, code style, tests, user docs and the agent skills that hold API and maintenance knowledge, CI and hosting, release, dependencies, and secrets. Load it before ad-hoc work on modules, tests, or docs in such a repo, for a question about these conventions, or when unsure which pywf-oss skill fits a job.
references/20-codecov.md
View on GitHub---
description: "codecov.yml versus .coveragerc, how the setup-codecov task stores the upload token on GitHub, the CI upload step, and fixing a failed or wrong upload. Read when connecting a repo to Codecov, or when the Codecov upload fails or its numbers look wrong."
---
# Codecov
---
## 1. Configuration
`codecov.yml` holds the report settings on the Codecov side. What gets measured is set by `.coveragerc` (`12-coverage.md`).
---
## 2. Upload token
`mise run setup-codecov` uses `CODECOV_TOKEN`, the account **API** token (`01-secrets.md`), to fetch the repo's own upload token, and stores it as the `CODECOV_TOKEN` Actions secret of the GitHub repo. The task is idempotent, and runs only after the user's yes (`03-mise.md`).
---
## 3. Upload in CI
The last workflow step (`19-github-actions.md`) uploads `coverage.xml` with `codecov/codecov-action`. The report path goes in the `files:` input; the old `file:` input is gone.
---
## 4. Diagnosing
| Symptom | Fix |
| :--- | :--- |
| "Upload coverage to Codecov" fails | The `CODECOV_TOKEN` Actions secret is missing or stale. Check with `gh secret list` (names only), then rerun `mise run setup-codecov`. |
| The upload succeeds, but the numbers look wrong | Compare `.coveragerc` `omit` with the `--cov=<package_name>` target, and check that the test step produced `coverage.xml`. |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |