generate_repo_overview: configure and select Reference Integration branches
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 28/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- html, python
調査の方向性
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.jsonfrom 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
- 平均マージ
- 1日 19時間
- マージ済み PR（30日）
- 10
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
eclipse-score/.github のほかの issue
-
難易度 5/5 1週間以上 初心者へのやさしさ 15/100
eclipse-score/.github#125 ·
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 22/100
eclipse-score/.github#123 ·
メンテナーはふだん 1 日以内に返信
-
configure dependabot対応中かも @AlexanderLanin が 11 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 55/100
eclipse-score/.github#120 ·
メンテナーはふだん 1 日以内に返信
-
good first issue
難易度 3/5 1〜2日 初心者へのやさしさ 55/100
eclipse-score/.github#115 ·
メンテナーはふだん 1 日以内に返信
eclipse-score/.github の issue をすべて見る
似ている issue
-
[Resource]: Loreオープンresource-submission validation-passed
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
hesreallyhim/awesome-claude-code#3234 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
openminion/openminion#376 ·
メンテナーはふだん 1 日以内に返信
-
Type: ☹︎ Bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
posit-dev/great-tables#1028 ·
メンテナーはふだん 1 日以内に返信
-
integration: apple_tv
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
home-assistant/core#188282 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
A "since" range is worded as a career: "the past two seasons" says "regular season career (2025 on)"オープンP4: low
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
jeffknupp/association#538 ·