nodejs / nodejs/github-bot

Auto comment/close wrong-repo issues

未關閉
#162 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

主要語言
JavaScript
星號
305
分支
148
平均合併
9 小時 2 分鐘
30 天內合併 PR
3

描述

We get a lot of issues raised that basically need to be closed with a link to the relevant repo. @mscdex does a heroic job of commenting (I assume with a saved reply) and closing all these1, but it seems like something that could be automated. Having a bot do that would (IMO) make it feel less personal for the person whose issue is being closed.

1 See for example https://github.com/nodejs/node/issues/16710#issuecomment-341699548

Proposal

If someone adds the wrong-repo label, the bot comments and closes the issue. @mscdex 's comment text seems perfect as a stock comment.

General help questions should be posted to the nodejs/help issue tracker instead. This issue tracker is for reporting bugs and submitting feature requests for node core. Issues with npm or other tools that use node should be posted to the appropriate issue tracker for those tools, unless it can be proven that the issue is in fact with node core and not the tool in question.

Follow-on proposal

What might be even more helpful is if a collaborator adds the question and wrong-repo labels, the github-bot "moves" the issue to nodejs/help.

Moving would mean:

  • Raising a new issue in nodejs/help @mentioning the original issue raiser and linking to the original issue.
  • Closing the nodejs/node issue with a stock comment linking to the new issue.

貢獻指南

開啟貢獻指南

從這裡開始

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

研究方向

先檢視 github-bot 儲存庫現有對 labels、留言、關閉 issue 及建立 issue 的處理方式;未指定特定檔案或測試。Done 應涵蓋提議的 wrong-repo 自動化,並釐清後續移至 nodejs/help 是否包含在內,同時針對產生的留言、連結及狀態變更提供測試或有文件記錄的驗證。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
javascript
領域
tooling
Issue 類型
功能
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
基本清楚
新手友好度
35/100

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

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