fix(ci): AI review lanes skip on a bot commit, leaving the PR head unreviewed for the merge gate
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 28/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github-actions
- 领域
- ci-cd
调研方向
Start from the review lanes' trigger conditions and the skip logic for commits authored by bots, and from the merge gate that holds on a skipped lane, which the /source-control:pull-request step uses. Then check why the first ready event on the PR started no CI. Done means one of the two proposed approaches is chosen and documented in the merge gate, and the ready trigger behaviour is explained or fixed. The maintainer has not yet picked an approach, so confirm the direction before writing code.
由索引模型根据 Issue 内容生成。
描述
Problem
On #6913 (2026-10-11), a docs-cleanup commit by melodic-automation-lanes[bot] (1289a56b3a, 4 wording-only lines) landed on the PR head after the last human-driven push. Both AI review lanes ended skipped on that head, apparently because a bot authored the commit. The /source-control:pull-request merge step holds on a skipped review lane, and the standing merge rule requires the AI reviews to have finished on the head. So the PR either deadlocks or merges on an exception. #6913 merged on an exception: the agent read the bot's 4-line diff itself, and the previous head's security review had passed and its code review had posted "No findings".
A related symptom on the same PR: the first ready event started no CI, and the agent had to flip the PR back to draft and to ready again.
Proposed next step
Pick one and document it in the merge gate:
- Run the review lanes on bot commits to PR branches, at least for the docs-cleanup bot.
- Or let the gate carry forward a review verdict from the prior head when the only later commits come from an allowlisted bot and change wording only.
Separately, check why the first ready event did not trigger the lanes.
- 主要语言
- Shell
- 星标
- 22
- 派生
- 2
- 平均合并
- 8 小时 24 分钟
- 30 天内合并 PR
- 947
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
melodic-software/claude-code-plugins 的其他 Issue
-
needs-human needs-triage 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 天内回复
-
knowledge: docpage-digest dual verification defines no verdict vocabulary or pass/fail threshold未关闭needs-human
难度 2/5 1-3 小时 新手友好度 78/100
melodic-software/claude-code-plugins#7286 · 2 条评论 ·
维护者通常 1 天内回复
查看 melodic-software/claude-code-plugins 的全部 Issue
相似的 Issue
-
Dev
难度 2/5 1-3 小时 新手友好度 62/100
ankidroid/Anki-Android#22555 ·
维护者通常 1 天内回复
-
Add .gitignore可能已有人在做 @ajeanmahoney 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100
-
难度 1/5 1 小时以内 新手友好度 75/100
tesseract-ocr/tesseract#4653 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 74/100
维护者通常 1 天内回复
-
documentation good first issue
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复