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 摘要。