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

feat(work-items): keep status: needs-decision and status: needs-info items off the autonomous frontier

已关闭 适合新手
#7,995 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

已经有一个关联 PR 被合并了。

  • #8159 来自 @melodic-automation-lanes —— 已合并

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
88/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
shell
领域
ai, cli

调研方向

首先查看 wit_filter_frontier 使用的人工下限标签集,然后检查 frontier 测试文件和 tracker 契约的 list-frontier 部分。添加测试覆盖,证明两个状态标签都会排除自主项,但仍保留在非自主 frontier 中,并更新契约和 work-items 的 changelog 片段。对 frontier 测试运行 scripts/run-test-file.sh,并运行 scripts/check-changelog-fragments.sh;所有列出的用例和检查均通过即表示完成。

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

描述

needs-human work-class: scoped

Refs: #6993

Agent Brief

Type: Feature
Summary: list-frontier --autonomous excludes items labeled status: needs-decision or status: needs-info, as the owner decided on 2026-10-13.

Current behavior:
With --autonomous, the core frontier derivation excludes items labeled needs-human and items carrying a human-floor label (work-class: structural, work-class: untrusted-provenance, provenance: signal). An item carrying both agent-ready and status: needs-decision stays on the autonomous frontier; #6075, #6078 and #6079 were in that state.

Desired behavior:

  • With --autonomous, an item labeled status: needs-decision or status: needs-info is excluded, even when it also carries the autonomous-eligible role label.
  • Without --autonomous, those items stay on the frontier.
  • The tracker contract's list-frontier section names both labels in the autonomous floor.
  • The label names are defined once, beside the existing human-floor label lists, and not restated elsewhere.

Key interfaces:

  • Human-floor label set used by wit_filter_frontier: gains the two status labels.
  • Tracker contract, list-frontier --autonomous floor: documents them.

Acceptance criteria:

  • scripts/run-test-file.sh on the frontier test file passes, including new cases: an agent-ready item with status: needs-decision is excluded under --autonomous; one with status: needs-info is excluded; both stay on the non-autonomous frontier.
  • The contract's autonomous-floor paragraph names both labels (read from the diff).
  • A changelog fragment for work-items is added and scripts/check-changelog-fragments.sh passes.

Out of scope:

  • Making the status labels remappable through binding role_labels.
  • Lane claim and report behaviour (sibling children).
  • Triage or attend-queue label handling.

This was generated by AI during backlog shaping. Split from #6993; the owner approved filing it in an attended backlog-shaping session on 2026-10-18.

主要语言
Shell
星标
22
派生
2
平均合并
7 小时 8 分钟
30 天内合并 PR
874

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

melodic-software/claude-code-plugins 的其他 Issue

查看 melodic-software/claude-code-plugins 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

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