Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

generate_repo_overview: configure and select Reference Integration branches

未关闭
  • 哪里不对？
#124 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
28/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
html, python
领域
build-system, developer-experience

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
Python
星标
0
派生
14
平均合并
19 小时 31 分钟
30 天内合并 PR
11

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

eclipse-score/.github 的其他 Issue

查看 eclipse-score/.github 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。