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

Add Unused Dependency Check for Ruby Gems

Abierto
  • ¿Algo no está bien?
#63 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
ruby
Área
ci-cd, tooling

Línea de trabajo

Start by reviewing the main CI workflow and the current Gemfile, then investigate whether degem works reliably and compare the suggested alternatives bundle-checker and gem-unused. Done means a stable dependency check is integrated, reports current unused gems, handles documented false positives, and fails CI when unused dependencies are detected.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

feat: Add Unused Dependency Check for Ruby Gems

Description:
To maintain a clean and efficient codebase, we need to add an automated process to the zitadel/client-ruby CI pipeline. The goal of this process is to detect and report any gems listed in the Gemfile that are no longer used in the project. The initial tool considered for this task was degem.

Problem:
The proposed tool, degem, does not appear to be functional in our current environment. Further investigation suggests the tool may be unmaintained, with its last commit several years ago. This makes it an unreliable choice for our CI pipeline, as it may have compatibility issues with modern Ruby versions and bundler.

Impact:

  • Without an automated check, the project is at risk of accumulating unused dependencies over time.
  • Unused gems lead to project bloat, slower bundle install times, and an increased potential security surface.
  • The dependency tree is less clear, making maintenance more difficult for developers.

Tasks:

  1. Attempt a final investigation to determine if degem can be made to work reliably.
  2. If degem is not viable, research and evaluate alternative tools for detecting unused Ruby gems (e.g., bundle-checker, gem-unused).
  3. Select a reliable tool and integrate it into the CI pipeline as a new check.
  4. Run the tool on the codebase and generate an initial report of unused dependencies.
  5. Configure the tool to ignore any known false positives (e.g., gems used by frameworks or other tools but not directly required in the code).
  6. Create a follow-up pull request to remove the confirmed unused gems from the Gemfile.

Expected Outcomes:

  • The CI pipeline includes a job that automatically fails if it detects unused gems in the Gemfile.
  • The project's dependencies are kept clean and minimal, improving maintainability and reducing bloat.
  • Developers are immediately notified of unused dependencies when contributing code.

Additional Notes:

  • The primary goal is to establish a reliable dependency check, not necessarily to use degem. The chosen solution should be stable and actively maintained.
  • This task will likely require updating the main CI workflow file to add a new step for the dependency analysis.
Lenguaje dominante
Ruby
Estrellas
6
Forks
2
Merge medio
11 min
PR fusionados (30 d)
2

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin 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 zitadel/client-ruby

Todos los issues de zitadel/client-ruby

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.