test(source-control): give the pull-request eval cases a gh fixture so ready runs reach the flip
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- git, github, shell
- 领域
- devtools, testing-qa
调研方向
Start with plugins/source-control/evals/pull-request-ready-hands-pr-to-explain-change/scaffold.sh and the ready phase's gh pr view lookup (§2.5.1) in the pull-request skill. The mechanism is undecided: choose between a gh shim the scaffold puts on PATH (check the sandbox's PATH first) and a fixture convention in the /evals:plugin-eval case-authoring reference. Done when the ready cases reach gh pr ready in a kept-trace run.
由索引模型根据 Issue 内容生成。
描述
Context
Found in review of #6987 (Codex finding on plugins/source-control/evals/pull-request-ready-hands-pr-to-explain-change/scaffold.sh).
Problem
The source-control plugin-eval cases for /source-control:pull-request (pull-request-ready-merges-base-never-rebases, pull-request-ready-hands-pr-to-explain-change, and likely the merge and dirty-worktree cases) scaffold only a local git repository: no remote, no pull request, and no gh fixture. The skill's ready phase first resolves the PR (gh pr view, §2.5.1) and stops when that fails, so a correct run never reaches the steps these cases grade (the base merge, gh pr ready, the explain-change hand-off). The graders can then pass only on a run that ignores a failed lookup.
No case in the repository stubs gh today, and a case cannot set PATH (env keys are limited to EVAL_*), so the fix needs a decided mechanism.
Suggested fix
Decide how a plugin-eval case presents a forge to the skill: a gh shim the scaffold installs where the run's PATH finds it (verify the sandbox's PATH first), or a documented fixture convention in /evals:plugin-eval's case-authoring reference. Then apply it to every pull-request case that calls gh, and confirm with a kept-trace run that the ready cases reach gh pr ready.
Related: #6107, #6987
- 主要语言
- Shell
- 星标
- 22
- 派生
- 2
- 平均合并
- 8 小时 25 分钟
- 30 天内合并 PR
- 944
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
melodic-software/claude-code-plugins 的其他 Issue
-
good first issue priority: low
难度 2/5 1-3 小时 新手友好度 62/100
melodic-software/claude-code-plugins#7530 · 1 条评论 ·
维护者通常 1 天内回复
-
needs-human priority: medium
难度 2/5 1-3 小时 新手友好度 65/100
melodic-software/claude-code-plugins#7455 · 1 条评论 ·
维护者通常 1 天内回复
-
priority: medium
难度 2/5 1-3 小时 新手友好度 68/100
melodic-software/claude-code-plugins#7351 · 2 条评论 ·
维护者通常 1 天内回复
-
agent-ready priority: high work-class: scoped
难度 2/5 1-3 小时 新手友好度 74/100
melodic-software/claude-code-plugins#7312 · 3 条评论 ·
维护者通常 1 天内回复
-
priority: medium
难度 2/5 1-3 小时 新手友好度 76/100
melodic-software/claude-code-plugins#7288 · 2 条评论 ·
维护者通常 1 天内回复
查看 melodic-software/claude-code-plugins 的全部 Issue
相似的 Issue
-
area: compat area: parsing bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
Add dependabot未关闭feat
难度 2/5 1 小时以内 新手友好度 72/100
open-nudge/opentemplate#204 ·
维护者通常 1 天内回复
-
omarchy-brightness-keyboard: double idle-blank saves brightness 0, so wake 'restore' keeps the keyboard backlight off可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
Type/Improvement
难度 2/5 1-3 小时 新手友好度 62/100
wso2/product-integrator-mi#5099 ·
维护者通常 1 天内回复
-
[Bug] Windows 上 pwsh 工具名未按 exec 分类着色，与状态圆点颜色家族分裂可能重新可做 关联的 PR 已关闭且未合并。 未关闭
难度 2/5 1-3 小时 新手友好度 62/100
ccch1mneyyy/dsh-TUI#1555 ·
维护者通常 1 天内回复