Turn pack proposals into generation pull requests, triggered by a maintainer label
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 38/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- github-actions, typescript
Direzione di ricerca
Read .github/ISSUE_TEMPLATE/content_pack_proposal.yml, .github/labels.json, and packages/cli/src/generate/, then review the referenced pipeline documentation and ADR. Map the issue form fields to the generator inputs and inspect how GitHub Actions handles issue events, permissions, and secrets. Done when the acceptance criteria pass, including injection safety, permission checks, successful and failed run behavior, and updated documentation.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Context
The content pack proposal form exists, and lexvm generate can produce a verified pack. Connecting them lets the community propose adventures that the project generates and reviews in the open. Every run costs API usage, so only a maintainer may start one. Needs a measured real run of lexvm generate (#40), the licensing decision (ADR 0010) and the provenance policy first.
Scope
- Extend .github/ISSUE_TEMPLATE/content_pack_proposal.yml with the inputs
lexvm generateneeds: idea, language, target minutes, pack id (kebab-case), license (SPDX) and author credit. - A new trigger label (for example
generate: approved) in .github/labels.json. - Workflow
generate-pack.ymlonissues: labeled: runs only when that label is added by a user with write or maintain permission (checked through the API, not only by label presence). - Input handling: parse the form fields with a script; issue text is passed through files or environment variables and never interpolated into shell commands; validate the pack id pattern, language and a minutes range.
- Generation:
ANTHROPIC_API_KEYfrom a protected environment, model from a repository variable; cost caps through--max-repairs,--max-tokens, a job timeout and a concurrency group of one; the trigger label is removed after the run. - Result: a branch
pack/<id>and a pull request with the pack, design/ and design/run.json; the PR body has thelexvm checksummary, token totals, the provenance and a link to the proposal; labelscontent-packandarea: content. - A comment on the proposal with the outcome. On failure: the diagnostics summary and the artifacts, and no pull request.
- Least-privilege permissions per job.
Acceptance criteria
- Adding the label as a user without write permission does nothing (tested).
- A proposal with shell metacharacters and
${{ }}in its text cannot inject commands (tested). - A successful run opens a pull request that passes CI.
- A failed run comments the diagnostics and opens no pull request.
- The token usage of each run is reported in the pull request.
- docs/authoring/pipeline.md and CONTRIBUTING.md describe the process.
References
- .github/ISSUE_TEMPLATE/content_pack_proposal.yml
- .github/labels.json
- packages/cli/src/generate/
- docs/authoring/pipeline.md
- docs/adr/0007-llm-pipeline-byo-prompt-kit-and-api-generator.md
- SECURITY.md (Scope)
- Lingua principale
- TypeScript
- Stelle
- 0
- Fork
- 0
- Merge medio
- 28m
- PR unite (30g)
- 2
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di nullthrone/lexvm
-
area: web good first issue priority: low type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
nullthrone/lexvm#49 ·
-
area: infra good first issue priority: low type: chore
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
nullthrone/lexvm#41 ·
-
area: engine good first issue priority: low type: feature
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
nullthrone/lexvm#27 ·
-
area: web priority: low type: research
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
nullthrone/lexvm#63 ·
-
area: infra area: web priority: medium type: chore
Difficoltà 5/5 Più di una settimana Idoneità per principianti 38/100
nullthrone/lexvm#62 ·
Tutte le issue di nullthrone/lexvm
Issue simili
-
area: image-engine bug priority: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
snapotter-hq/SnapOtter#3885 ·
I maintainer di solito rispondono entro 1 giorno
-
Mend: dependency security vulnerability
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 3 giorni
-
pending triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
bug P3 UI/UX
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
openclaw/openclaw#182077 · 1 commento · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno