Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .claude/skills/create-ticket/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/<owner>/<repo>/labels/<name> fails), POST repos/<owner>/<repo>/labels with that name before filing.
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/dev-work.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/epic.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/idea.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/spike.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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 `<area>: <approach>`, 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:
Expand Down
Loading