Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#7,207 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
github, shell
Domaine
backend-api-design, tooling

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Shell
Étoiles
22
Forks
2
Merge moyen
8 h 25 min
PR mergées (30 j)
944

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de melodic-software/claude-code-plugins

Toutes les issues de melodic-software/claude-code-plugins

Issues similaires

Plus d'issues Shell/Bash

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.