Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#6,993 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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分
マージ済み PR（30日）
902

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

melodic-software/claude-code-plugins のほかの issue

melodic-software/claude-code-plugins の issue をすべて見る

似ている issue

Shell/Bash の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。