mirror of
https://github.com/OpenRouterTeam/spawn.git
synced 2026-04-28 20:09:34 +00:00
f7c6e07867
* feat: security triage now applies full label taxonomy Triage mode now applies: - Safety label (safe-to-work / malicious / needs-human-review) - Content-type label (bug, enhancement, security, question, etc.) - Lifecycle label (Pending Review) so downstream teams can pick up Team-building mode now transitions lifecycle labels: - Adds "In Progress" at start, removes it on close Added a "Available Labels Reference" section to the triage prompt documenting all label categories for the agent. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * feat: all security-filed issues get safe-to-work + Pending Review Issues filed by the security team (scan findings, drift/anomaly reports, follow-up issues from closed PRs) now automatically get `safe-to-work` and `Pending Review` labels so downstream teams can immediately pick them up without waiting for another triage. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: remove Pending Review from safe-to-work issues safe-to-work already means triage is complete — adding Pending Review is redundant and confusing. Now only UNCLEAR issues get Pending Review (they still need human attention). SAFE issues and security-filed issues skip straight to actionable with just safe-to-work. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * refactor: normalize all labels to kebab-case Renamed on GitHub: - "In Progress" → "in-progress" - "Pending Review" → "pending-review" - "Under Review" → "under-review" - "good first issue" → "good-first-issue" - "help wanted" → "help-wanted" Updated all references in security.sh and refactor.sh to match. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: align issue templates and workflows with actual repo labels Created missing labels: cloud-request, agent-request, cli. Replaced nonexistent needs-triage with pending-review in all templates. Templates updated: - bug_report: bug + pending-review - cli_feature_request: cli + enhancement + pending-review - cloud_request: cloud-request + enhancement + pending-review - agent_request: agent-request + enhancement + pending-review Workflows updated: - refactor.yml: trigger on safe-to-work AND (bug|cli|enhancement|maintenance) - discovery.yml: already correct (safe-to-work AND cloud-request|agent-request) - security.yml: already correct (team-building label check) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Sprite <noreply@sprites.dev> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
51 lines
1.5 KiB
YAML
51 lines
1.5 KiB
YAML
name: CLI Feature Request
|
|
description: Suggest a new feature or improvement for the spawn CLI
|
|
title: "[CLI]: "
|
|
labels: ["cli", "enhancement", "pending-review"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for the suggestion! Describe what you'd like the spawn CLI to do.
|
|
|
|
- type: textarea
|
|
id: description
|
|
attributes:
|
|
label: Feature Description
|
|
description: What should the CLI do? Be as specific as you can.
|
|
placeholder: |
|
|
spawn should support a `--dry-run` flag that shows what would
|
|
be provisioned without actually creating anything.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: use-case
|
|
attributes:
|
|
label: Use Case
|
|
description: Why do you need this? What problem does it solve?
|
|
placeholder: |
|
|
I want to preview costs before spinning up a server.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: proposed-ux
|
|
attributes:
|
|
label: Proposed UX
|
|
description: How would you expect to use this feature? Show example commands or workflows.
|
|
placeholder: |
|
|
$ spawn claude hetzner --dry-run
|
|
Would create: Hetzner CX22 in fsn1 (~$0.01/hr)
|
|
Run without --dry-run to proceed.
|
|
render: shell
|
|
validations:
|
|
required: false
|
|
|
|
- type: textarea
|
|
id: additional
|
|
attributes:
|
|
label: Additional Context
|
|
description: Any other details, mockups, or references to similar tools
|
|
validations:
|
|
required: false
|