From 44b9673e1733cc47c187f593757fcb8a964f1e9f Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 18 Nov 2026 22:13:15 +0000 Subject: [PATCH] #93 - label Delphi issues with their workspace scope Each issue template asks for the scope label (the dotted workspace name, or main) next to the written-by label, and Delphi's create-ticket applies it from the filing workspace's workspace.yml name, creating the label first if missing. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_013vbA3iKVfvhFrgVECq2K4Z --- .claude/skills/create-ticket/SKILL.md | 1 + .github/ISSUE_TEMPLATE/dev-work.yml | 1 + .github/ISSUE_TEMPLATE/epic.yml | 1 + .github/ISSUE_TEMPLATE/idea.yml | 1 + .github/ISSUE_TEMPLATE/spike.yml | 1 + 5 files changed, 5 insertions(+) diff --git a/.claude/skills/create-ticket/SKILL.md b/.claude/skills/create-ticket/SKILL.md index 11a8ef1..afff1c1 100644 --- a/.claude/skills/create-ticket/SKILL.md +++ b/.claude/skills/create-ticket/SKILL.md @@ -9,3 +9,4 @@ Follow the shared rules in `software/application-software/workspace-inherit/.cla - Labels: the template's category and a written-by label; Delphi has no area labels. - Vocabulary: `docs/design.md`'s terms (workspace, ws branch, refresh, propose, `workspace-inherit/`). - Diagrams: show the branches and folders a change touches (main, `ws/*`, `.delphi/`, CI), before and after. +- Scope label: also label it with the filing workspace's name, the `name:` in its root `workspace.yml`. A main checkout has none: ask which workspace the issue came from (`main` if none). If the label is missing on the repo (GET repos///labels/ fails), POST repos///labels with that name before filing. diff --git a/.github/ISSUE_TEMPLATE/dev-work.yml b/.github/ISSUE_TEMPLATE/dev-work.yml index 6eb6751..290fdb2 100644 --- a/.github/ISSUE_TEMPLATE/dev-work.yml +++ b/.github/ISSUE_TEMPLATE/dev-work.yml @@ -8,6 +8,7 @@ body: One template for all implementation work. Set the issue **type** (Feature, Bug, or Task) instead of picking a different template. If this belongs to an epic, add it as a sub-issue of the epic. After filing, add a written-by label (`by: human`, `by: ai`, `by: ai-assisted`). + Also add the scope label: the dotted name of the workspace it came from (like `s.app.argos.argos-dev`), or `main`. - type: textarea id: what attributes: diff --git a/.github/ISSUE_TEMPLATE/epic.yml b/.github/ISSUE_TEMPLATE/epic.yml index 8853a14..1e4076b 100644 --- a/.github/ISSUE_TEMPLATE/epic.yml +++ b/.github/ISSUE_TEMPLATE/epic.yml @@ -9,6 +9,7 @@ body: An epic groups dev work tickets; link them as sub-issues. If it came from an idea or spike, link it below and close it as completed. After filing, add a written-by label (`by: human`, `by: ai`, `by: ai-assisted`). + Also add the scope label: the dotted name of the workspace it came from (like `s.app.argos.argos-dev`), or `main`. - type: input id: from attributes: diff --git a/.github/ISSUE_TEMPLATE/idea.yml b/.github/ISSUE_TEMPLATE/idea.yml index 78362e4..d4df93d 100644 --- a/.github/ISSUE_TEMPLATE/idea.yml +++ b/.github/ISSUE_TEMPLATE/idea.yml @@ -9,6 +9,7 @@ body: Keep an idea short. If it is small enough to just try, file a spike instead. Don't prescribe a solution. Each area stays open for one or more spikes to explore, not a chosen design. After filing, add a written-by label (`by: human`, `by: ai`, `by: ai-assisted`). + Also add the scope label: the dotted name of the workspace it came from (like `s.app.argos.argos-dev`), or `main`. - type: textarea id: idea attributes: diff --git a/.github/ISSUE_TEMPLATE/spike.yml b/.github/ISSUE_TEMPLATE/spike.yml index 828e03b..f777bb5 100644 --- a/.github/ISSUE_TEMPLATE/spike.yml +++ b/.github/ISSUE_TEMPLATE/spike.yml @@ -9,6 +9,7 @@ body: Don't prescribe a solution. Describe what to learn and leave the how to whoever picks it up. One approach per spike, not a set to choose between. Title it `: `, the area shared by its siblings. Prefer filing it under an idea (as a sub-issue), but a spike can stand alone. After filing, add a written-by label (`by: human`, `by: ai`, `by: ai-assisted`). + Also add the scope label: the dotted name of the workspace it came from (like `s.app.argos.argos-dev`), or `main`. - type: textarea id: exploring attributes: