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

generate_repo_overview: configure and select Reference Integration branches

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

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
28/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
html, python
Área
build-system, developer-experience

Línea de trabajo

Start in generate_repo_overview, where the Reference Integration's MODULE.bazel (and included module files) and known_good.json are read from the default branch, and trace how that data reaches the HTML dashboard. Design the per-ref configuration and cache layout first, since the issue leaves the format open and asks for a decision during implementation. Done when a main branch and a release branch with different pins can both be collected, appear in the dropdown with the default preselected, and switch repository inclusion and pins consistently, while missing refs are reported rather than silently falling back.

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

Descripción

Why

The overview should let users select which Reference Integration branch they want to inspect. The main development branch and release branches can integrate different repositories and pin different versions; users need to see the integration state relevant to their release.

Currently, generate_repo_overview reads the Reference Integration's MODULE.bazel (including included module files) and known_good.json from the repository's GitHub default branch. The generated dashboard therefore exposes only that integration state.

Expected behavior

  • Add configuration for the Reference Integration refs offered in the dashboard:
    • Main development branch, with a configurable branch name and a default selection.
    • Release branches, selected through an explicit list and/or configurable branch patterns; the exact configuration format can be decided during implementation.
  • Add a dropdown to the HTML dashboard to switch between the collected Reference Integration refs. Clearly show the selected branch.
  • Switch all Reference Integration-derived information consistently, including repository inclusion, pinned versions/commits, and comparisons based on those pins. Read module files and known_good.json from the same selected ref.
  • Collect and persist the data for each configured ref so switching works on the generated static site without live GitHub API access. Keep cached data separate by ref and record the resolved commit for traceability.
  • Preserve the current default-branch behavior when no additional refs are configured. Document how the selected default applies to outputs without an interactive selector.

Optional extension: pull requests

Consider making Reference Integration pull requests available in the same selector, controlled by configuration. This would allow inspecting proposed integration updates before they are merged. If included, define whether the data represents the PR head or its merge result and label the PR and resolved commit clearly. PR support can follow separately from branch selection.

Acceptance criteria

  • Configure a main branch and at least one release branch with different integration pins.
  • Both appear in the dropdown, with the configured default selected initially.
  • Switching branches updates repository inclusion and pin-related values consistently, including any corresponding detail view.
  • Refreshing or collecting one ref does not reuse or overwrite another ref's integration data.
  • Missing or unavailable configured refs are reported clearly rather than silently displaying default-branch data.
Lenguaje dominante
Python
Estrellas
0
Forks
14
Merge medio
19 h 31 min
PR fusionados (30 d)
11

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 eclipse-score/.github

Todos los issues de eclipse-score/.github

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.