whitesmith / whitesmith/rubycritic
Coverage index page of "Build" shows 0 coverage if compare view
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 3.5k
- Forks
- 234
- PR merge metrics
- No merged PRs in 30d
Description
If compare view (--branch BRANCH or --mode-CI BRANCH is used), a coverage index page shows the names of changed files, with 0% coverage.
If I switch to the `main` or `rubycritic-setup` branch from the above menu, their coverage index pages shows non-zero coverages.
"Build" compare/simple_cov_index.html |
target branch compare/main/simple_cov_index.html |
source branch compare/rubycritic-setup/simple_cov_index.html |
|---|---|---|
 |
 |
 |
I expect the "Build" coverage index page shows the coverages of the changed files.
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 tracing the compare-view paths selected by --branch BRANCH and --mode-CI BRANCH, then inspect how compare/simple_cov_index.html is generated versus the target and source branch pages. Reproduce the zero-coverage Build output and verify that the changed files in the generated index show their actual coverage values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100