Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#7,207 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github, shell
Ambito
backend-api-design, tooling

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
8h 24m
PR unite (30g)
947

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di melodic-software/claude-code-plugins

Tutte le issue di melodic-software/claude-code-plugins

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.