Skip to content

Label each PR with its ticket's category - #82

Merged
bracyw merged 1 commit into
mainfrom
pr-ticket-category-label
Oct 25, 2026
Merged

bracyw merged 1 commit into
mainfrom
pr-ticket-category-label

Conversation

@bracyw

@bracyw bracyw commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

Changes

open-pr now adds the ticket's category label to every PR it opens, alongside the project's labels, taken from create-ticket's label list. Only spikes and dev work get PRs, so in practice that is spike or dev work; ideas and epics never have their own PR. Argos's and Nero's pr-conventions drop their "no category label" / "none" rules to match.

Diagram

flowchart LR
  I[Idea] --> S[Spike] -->|draft PR, label: spike| P1[(PR)]
  I --> E[Epic] --> D[Dev work] -->|PR, label: dev work| P2[(PR)]
  S -.->|standalone| D
  classDef none stroke-dasharray: 4 4
  class I,E none
Loading

Dashed boxes (idea, epic) never get a PR, so never get a PR category label.

Testing

  • ci/check.sh and tests/e2e.sh (119 checks) pass; skill text only, no script behaviour changed
  • Applied by hand to Argos's 14 open spike PRs, which now carry the spike label

Notes

  • Nero's PRs previously got no labels at all; they now get the category label only. Nero's repo needs the spike and dev work labels if it lacks them.

Checklist

  • ci/check.sh and tests/e2e.sh pass
  • Version bumped if a manifest file changed (none changed)
  • No merge conflicts
  • Request reviewers & ping on Slack

Generated by Claude Code

@bracyw bracyw added the by: ai-assisted Written by a person with AI help label Oct 20, 2026 — with Claude
@bracyw bracyw self-assigned this Oct 20, 2026
@bracyw
bracyw marked this pull request as ready for review October 25, 2026 02:42
@bracyw
bracyw merged commit 83fa970 into main Oct 25, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

by: ai-assisted Written by a person with AI help

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants