Repository navigation
Add Codecov upload and PyPI release workflow - #2
Merged
Merged
Conversation
The README badges for coverage and released version need something behind them. Two pieces: - tests.yml runs the suite under `coverage` and uploads coverage.xml to Codecov from the 3.11 matrix entry only; the matrix differs in interpreter version, not in which lines execute, so three uploads would be redundant. Coverage scope lives in pyproject.toml and omits the vendored MONAI transforms, matching their existing ruff and mypy exemptions. - python-publish.yml builds an sdist and wheel on a `v*` tag push, which is the release step CONTRIBUTING.md already documents, and publishes via PyPI Trusted Publishing so there is no long-lived API token in the repo secrets. Codecov thresholds are informational: at 32% line coverage a hard gate would only block pull requests that are not the cause. Both badges render as "unknown"/"not found" until the repository is added on Codecov and the first release is published. CONTRIBUTING.md documents both one-time setup steps. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README badges for coverage and released version need something behind them. Two pieces:
coverageand uploads coverage.xml to Codecov from the 3.11 matrix entry only; the matrix differs in interpreter version, not in which lines execute, so three uploads would be redundant. Coverage scope lives in pyproject.toml and omits the vendored MONAI transforms, matching their existing ruff and mypy exemptions.v*tag push, which is the release step CONTRIBUTING.md already documents, and publishes via PyPI Trusted Publishing so there is no long-lived API token in the repo secrets.Codecov thresholds are informational: at 32% line coverage a hard gate would only block pull requests that are not the cause.
Both badges render as "unknown"/"not found" until the repository is added on Codecov and the first release is published. CONTRIBUTING.md documents both one-time setup steps.