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

Lanes: carry over findings from the Claude Projects trial (merge path, gating, reports)

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
12/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
github
领域
ai, tooling

调研方向

This is a design issue for the agent lanes tracked in #6958, not a code change. Start with the list-frontier --autonomous filter in work-items/tools/work-item-tracker/CONTRACT.md (lines 207-215) and the PRs #6839, #6911, #6912 and #6932 for the observed behaviour. Done means the lane design states the pickup rule, merge gate and merge call, plus a claim mechanism and per-run report comments.

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

描述

needs-human needs-triage

Context

On 2026-10-10 and 10-11 we trialed Anthropic's Claude Projects (beta) as the autonomous build stage for this repo's agent-ready issues. Four PRs merged: #6839, #6911, #6912 and #6932. Three of them merged with no operator action. We decided not to use Projects as the main pipeline: a project belongs to one claude.ai account and can't be shared or synced, which conflicts with rotating accounts. The findings below apply to the agent lanes (#6958) instead.

Findings to reuse

  1. Pickup rule. Use the list-frontier --autonomous filter (work-items/tools/work-item-tracker/CONTRACT.md:207-215), then also require agent-ready and exclude status: needs-decision and status: needs-info. Three issues carried agent-ready and needs-decision together (#6075, #6078, #6079). The filter alone would have picked them up.
  2. Merge gate. Wait for ci-status green on the head commit, all review threads resolved, and every AI review finished, Codex included. Threads that waited for Codex caught real findings in #6839 and #6912.
  3. Merge call over REST. PUT /repos/{o}/{r}/pulls/{n}/merge-async with merge_action=merge_queue and sha=<head> returned enqueued every time. Plain PUT .../merge "does not support ... merging with a merge queue" (GitHub REST docs). REST can't take a PR out of draft, so open PRs as ready.
  4. Review threads. Cloud threads replied to and resolved Codex review threads themselves (#6839, #6912). This is evidence for #6810.
  5. Signed commits. Every commit pushed by a thread, and every merge commit, showed verified: true.
  6. Reports. Each run posts a final report as a PR comment: what it did, the merge call, and every failed API call. That gave the operator full visibility without reading transcripts.
  7. Permission-classifier friction. Auto mode sometimes refused gh api writes ("External System Writes", "Unrequested Commit in a Connected App"), including opening a PR and assigning an issue. Threads fell back to the GitHub MCP tools. A lane needs an explicit permission policy for these writes.
  8. Claim gap. No run could reliably claim an issue before opening its PR (the assign call was blocked). Two lanes working the same frontier at once could start the same issue.

Acceptance criteria

  • The lane design under #6958 states its pickup rule, merge gate and merge call, and covers points 1–3.
  • The lane has a claim mechanism that holds while several lanes run at once (point 8).
  • Every lane run posts a report comment on its PR (point 6).

🤖 Generated with Claude Code

https://claude.ai/code/session_01LGDKQK7XJf6kz6EZDzbKwM

主要语言
Shell
星标
22
派生
2
平均合并
6 小时 42 分钟
30 天内合并 PR
902

环境准备

  • 没有 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 摘要。