Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

chore: add labels for a clear reproductive steps flow

未关闭
#19 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
领域
tooling

调研方向

Start with the issue's three requirements: define the reproductive-steps flow chart, identify the labels needed to support it, and determine the scope of the waiting-for-response bot. Done means the flow is documented, the supporting labels are specified, and the bot behavior or a separate task for it is clearly defined.

由索引模型根据 Issue 内容生成。

描述

chore
Description

Cross posting from internal conversations:

As a side note, it would be ideal if we add a tag named something like needs reproductive confirmation or similar where the description is: The issue needs confirmation from developers that it has been reproduced .


Looking into the future we should do something like:

  • Check if the issue has reproductive and clear reproductive steps:
    • Add the "has reproductive steps" label if it has together with "needs reproductive confirmation"
    • Add the "needs reproductive steps" label if it has not
  • Check those "has reproductive steps" issues can be reproduced
    • Add the "has been reproduced" if it was reproduced with a comment that details the steps and any additional context to reproduce
    • Add the "could not be reproduced" if it was not reproduced with a comment that details at what step the reproductive steps could not be followed together with the "waiting for response" label
    • If the "waiting for response" label persists for 2 weeks without any updated to comments we would have the BOT close the issue with a message along the lines of: ""Hey since this seems to be silent for a while, I am closing this for now. If anything comes up, don't hesitate on telling." (Credits to Renan, he usually used this as a template for his replies and I liked it and started using it).
Requirements
  • There is a defined flow chart explaining this flow
  • There are labels to support the flow outlined in the flow chart
  • There is a BOT that closes waiting for response issues (we could have a separate task for this effort if preferred)
Additional Context

No response

主要语言
没有语言数据
星标
6
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

相似的 Issue

更多 DevTools Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。