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

fix(work-items): label-provenance's body-edit check needs a path that works without GraphQL

未关闭
#7,240 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
github, shell
领域
tooling

调研方向

Start with plugins/work-items/tools/work-item-tracker/adapters/github/label-provenance.sh, then read #7009 and #7219 to understand the admission check and cloud GraphQL limitation. Verify whether the issue timeline or events API exposes body edit time using GitHub's API docs, or trace how unavailable reads are handled. Done means a cloud session admits a correctly labeled, unedited item or escalates it once with a clear reason, without silently refusing each cycle.

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

描述

needs-human needs-triage

Problem

#7009 makes label-provenance (plugins/work-items/tools/work-item-tracker/adapters/github/label-provenance.sh) refuse admission when an item's body was edited after its admitting label. It reads the body's last-edit time over GraphQL (lastEditedAt), because the REST API exposes no edit time. When that read fails, after_admission is null and the item is refused.

Cloud sessions get no GraphQL through the GitHub proxy (see #7219). So in a cloud session every item is refused: safe, but a cloud work-loop admits nothing.

Fix

Pick one:

  • Find a REST source for the body edit time, such as the issue timeline or an events endpoint, if one carries it. Verify against the API docs.
  • In a session without GraphQL, report the edit-time read as unavailable and route items to human attention once, instead of refusing every cycle.

Done when

  • A cloud session either admits a correctly labeled, unedited item, or escalates it once with a clear reason. It never refuses silently every cycle.

Refs: #7009

主要语言
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 摘要。