Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#6,993 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github
Área
ai, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
8 h 27 min
PR fusionados (30 d)
957

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.