Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#7,207 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
github, shell
Bereich
backend-api-design, tooling

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Shell
Sterne
22
Forks
2
Ø Merge
8 Std. 34 Min.
Gemergte PRs (30 T.)
946

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus melodic-software/claude-code-plugins

Alle Issues in melodic-software/claude-code-plugins

Ähnliche Issues

Weitere Issues zu Shell/Bash

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.