Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Migrate type labels to issue types and converge on a managed label set

オープン
  • 何か問題がありますか？
#11 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github, github-actions
領域
devops

調査の方向性

Start by reviewing the decision in #6 and the existing board reconciler and workflows in simp/gha-workflows; the issue also names Organization settings → Repository defaults → Repository labels for the UI-only step. The work spans scripts, organization settings, and a scheduled idempotent sync job across repositories. Done means the listed issues have matching types, obsolete labels are removed, managed labels converge, and the job reports unmanaged labels without deleting them.

索引モデルが issue の本文から書いたものです。

説明

needs-attention

Follow-up to the decision on #6: issue types replace per-repository type labels, and the remaining labels become a small set defined the same way in every repository.

Steps, in order

  1. Copy existing classification onto issue types. Set the type on every issue, open or closed, that carries bug (Bug) or enhancement (Feature): about 105 issues as of 2026-10-08. After this, removing the labels loses no history. (Script.)
  2. Delete the type labels and the never-used defaults from every repository: bug, enhancement, question, invalid, duplicate, wontfix, documentation. Apart from bug and enhancement, none of these has ever been applied to an issue in any repository. (Script; only after step 1 is verified.)
  3. Delete the status labels blocked, blocker and in progress (in every casing). The Org Triage board's Blocked and In Progress columns replace them, and every issue carrying them is closed. (Script.)
  4. Converge the managed set on every in-scope repository: the same name, colour and description everywhere for:
    • community, needs-attention (already consistent)
    • good first issue, help wanted. These are the names GitHub uses to surface issues to new contributors. Today they exist in 31 and 98 repositories respectively, in several colours.
  5. Update the organization's default labels to the managed set, so new repositories start clean. (UI only: Organization settings → Repository defaults → Repository labels.)
  6. Keep it converged. Add a small idempotent label-sync job, scheduled from simp/gha-workflows like the board reconciler, that creates or corrects the managed labels and reports (but doesn't delete) anything else. We decided against puppetsync for this: it works through PRs to files, and labels aren't files.
  7. Classify the unlabeled backlog gradually. 98 of 153 open issues have no type label. Set types at board reviews rather than in a bulk pass.

Not in scope

  • Labels on the vendored mirror forks, which have issues and PRs disabled.
  • Repository-specific labels that carry real meaning (for example upstream bug, refactor, do not merge). The sync job reports them; whether to keep each is decided separately.

Done when

  • Every open issue that had a type label has the matching issue type.
  • No in-scope repository has bug, enhancement, the unused defaults, or the status labels.
  • The managed labels are identical across in-scope repositories, and the sync job keeps them that way.
主要言語
言語のデータがありません
スター
0
フォーク
1
平均マージ
2日 14時間
マージ済み PR（30日）
2

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

simp/.github のほかの issue

simp/.github の issue をすべて見る

似ている issue

DevOps の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。