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

Set up GitHub Discussions as the entry point for unplanned work

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

@akolson がすでに取り組んでいます。

2026年9月29日 から。

評価

この issue はまだ評価されていません。

説明

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Overview

Contributors open issues asking to be assigned, and pull requests with no issue behind them. We have
no single place to evaluate that work, and no stated turnaround, so each case is handled ad hoc.

Establish GitHub Discussions as the entry point for unplanned work, and the process around it.

Complexity: Medium
Target branch: main

Context

#67 covered two halves. The automation half landed in #103, which acts on the issue a community pull
request closes. This issue tracks the other half, the process, which #67 describes in
https://github.com/learningequality/.github/issues/67#issuecomment-4174756496.

The reasons recorded there:

  • a place to talk about and evaluate work we did not plan
  • one pipeline, and somewhere to state our processing times
  • the ability to close an issue or pull request we cannot think through right now, while pointing
    the contributor somewhere to clarify first
The Change

Set up the Discussion. Create the category for unplanned work, and say in it what belongs there
and how long an answer takes.

Write the process. Say how an unplanned request is evaluated, who evaluates it, and what the
outcomes are.

Point contributors to it. Update the contributing guidelines and the bot messages that answer an
assignment request or an unlinked pull request, so they name the Discussion rather than leaving a
contributor to guess.

Out of Scope
  • The automation in #103.
  • Auto-closing pull requests with no linked issue. That is the stricter option below, and it waits
    on this process proving itself.
Acceptance Criteria
  • A Discussion category exists for unplanned work, and says what belongs there.
  • The stated turnaround is written down where contributors can read it.
  • The process says who evaluates a request and what the outcomes are.
  • The contributing guidelines point to the Discussion.
  • The bot messages that answer an assignment request point to the Discussion.
Follow-up

If the Discussion works, we can go stricter and auto-close every pull request with no linked issue,
with a note pointing to the Discussion. That would also let us auto-review the rest, even when the
issue is not linked correctly. #67 records this as a later decision, and it can come sooner if
unplanned pull requests become more frequent.

References
  • #67 is the parent. Its automation half is #103.
  • #104 gates a second issue assignment on an open pull request.
  • Slack thread with the
    original discussion.

AI usage

I used Claude Code to draft this issue from #67 and its comment thread. I decided the scope and the
split from the automation work.

主要言語
JavaScript
スター
1
フォーク
7
平均マージ
1日 10時間
マージ済み PR（30日）
4

環境構築

はじめの一歩

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

learningequality/.github のほかの issue

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

似ている issue

JavaScript の issue をもっと見る

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

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