Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[Proposal] Set up GitHub Discussions as the entry point for unplanned work

未關閉
  • 哪裡不對？
#105 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

@akolson 已經在處理了。

開始於 2026年9月29日。

評估

這個 Issue 還沒有評估資料。

描述

github_actions

❌ 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 天 8 小時
30 天內合併 PR
5

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

learningequality/.github 的其他 Issue

查看 learningequality/.github 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。