Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[REQUEST] Add support for branch comparison when code coverage has changed between branches

Abierto
#54 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@torresga ya está trabajando en esto.

Desde el 27/10/2025.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

enhancement Feature Request

Before we start...:

  • I checked the documentation and didn't find this feature
  • I checked to make sure that this feature has not already been requested

Branch/Commit:

main branch

Problem:

When using the -b option, the SkunkScore average doesn't change if you improve code coverage for your application/library.

Solution:

As a developer using skunk -b stable-branch
I want to see the right SkunkScore delta
So that I can quickly see how much I've improved my project by paying off tech debt

It could work like this:

skunk -b main
Switched to branch 'main'
running flay smells
...
running flog smells
.......................
running reek smells
.......................
running complexity
.......................
running attributes
.......................
running churn
.......................
running simple_cov
.......................
Switched to branch 'poc/compare-issue'
running flay smells
...
running flog smells
.......................
running reek smells
.......................
running complexity
.......................
running attributes
.......................
running churn
.......................
running simple_cov
.......................
Base branch (main) average skunk score: 32.21
Feature branch (poc/compare-issue) average skunk score: 27.21
**Code coverage average improved by 7.27%**
**Skunk score average is 15% better**

Notes:

It might be necessary to run the entire test suite "all over again" for one of the branches, so that we can compare two different result sets from SimpleCov.

I imagine it could work like this:

  1. Save a copy of the files for the current branch's coverage directory in a .skunk local directory
  2. Run all calculations for the current branch
  3. Switch to the "compared branch"
  4. Run the entire test suite using COVERAGE=true
  5. Save a copy of the files for the "compared branch" directory in a .skunk local directory
  6. Compare all results
  7. Output delta information
Lenguaje dominante
Ruby
Estrellas
547
Forks
33
Sin PR fusionados en 30 d

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fastruby/skunk

Todos los issues de fastruby/skunk

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.