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

fix(work-items): loop-lane identity follow-ups (app-slug config, telemetry issue capture, marker rule conflict)

Abierto
  • ¿Algo no está bien?
#7,207 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github, shell
Área
backend-api-design, tooling

Línea de trabajo

Read the four named telemetry scripts, plugins/work-items/reference/escalation-marker.md, and plugins/work-items/skills/work-loop/reference/c3-ratification-queue.md, along with the referenced issues #7202, #7203, and #7206 to understand the shared identity resolution order. Trace how configuration, issue authorship, status-comment identity, and marker rules are handled today. Done means each listed follow-up has a consistent fix and the C3 comment cannot be re-posted after its label is removed.

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

Descripción

area: security priority: medium

Follow-ups found while fixing #7161 (#7204) and #7167 (#7202). Each is pre-existing or newly exposed, and each needs its own fix.

  1. No config key supplies --app-slug. Under a GitHub App token, the telemetry scripts in work-loop (lane-telemetry-upsert.sh) and babysit-loop (telemetry-upsert.sh) now need --app-slug to resolve their write identity. Only the launch prompt can supply it today. Add one userConfig key shared by both lanes and harness-ops restart-consumer.sh (#7203).

  2. Anyone can capture the telemetry issue. The lane finds its telemetry issue by exact title match, and anyone can open an issue with that title. Require the issue's author to be the lane's write identity, using the same resolution order as #7202.

  3. Two rules on escalation markers conflict. plugins/work-items/reference/escalation-marker.md says a marker stands "only while it wears the role label". plugins/work-items/skills/work-loop/reference/c3-ratification-queue.md says "at most one, ever". Reconcile them so a C3 ratification comment can't be re-posted after the label is removed.

  4. harness-ops telemetry identity under App tokens. plugins/harness-ops/skills/lanes/scripts/telemetry-upsert.sh (around line 379) resolves its status-comment identity only through gh api user, so under an App token it finds no identity. Give it the same --app-slug resolution as #7202 and #7206.

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

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.