lance-format / lance-format/lance
test: run ci code coverage
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
It would occasionally be useful to check all added code paths in a PR are tested at least once and perhaps have a coverage viewer like codecov.
While percentage of coverage might not be the most useful metric it could prevent coverage regression.
Also Tarpulin seems like the most active github action for rust right now:
https://github.com/marketplace/actions/rust-tarpaulin
Contributor guide
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.
Research direction
Start by reviewing the repository's CI setup and the Rust Tarpaulin and Codecov links named in the issue. Determine how coverage should run for pull requests and what output should be published; done means added code paths can be checked and coverage regression is visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100