Skip to content

ci(triage): LABEL POLICY for ready-for-human issues — auto-apply needs-wg-review + domain #3479

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bokelley merged 1 commit into from
Apr 28, 2026
Merged

ci(triage): LABEL POLICY for ready-for-human issues — auto-apply needs-wg-review + domain #3479

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 4 additions & 0 deletions .changeset/triage-wg-label-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
---
---

Triage workflow now sends a LABEL POLICY directive to the routine for `ready-for-human` issues: apply `needs-wg-review` plus a domain label (`media-buy`, `signals`, `creative`, `brand`, `governance`, `sponsored-intelligence`, `schema`, `compliance-suite`, `addie`, `rfc`, etc.) so the working group can route from a single label query. PR-comment runs unchanged. Pure engineering issues (CI, deps, tooling) skip the WG labels.
15 changes: 14 additions & 1 deletion .github/workflows/claude-issue-triage.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,7 +199,20 @@ jobs:
"pr: " + $pr_block + "\n" +
"MODE: PR-feedback. Treat new comment as actionable feedback on the PR diff. If the comment requests a fix, apply it as a follow-up commit on the PR head branch — do not open a new PR. If the comment asks a question, answer it as a reply comment. If the comment is conversational with no action implied, post a short acknowledgement and stop.\n"
else
"is_pr: false\n"
"is_pr: false\n" +
"LABEL POLICY: When your triage status is `ready-for-human` (a real scope/policy/protocol decision is needed before code can land), apply the `needs-wg-review` label via `gh issue edit <num> --add-label needs-wg-review` AND apply the relevant domain label so the working group queue can route. Domain label vocabulary (pick one or more that match the issue's subject area):\n" +
" - media-buy — campaign / order / package / pricing / makegood / measurement\n" +
" - signals — audience / signal-marketplace / activation / data-clean-room\n" +
" - creative — assets / format / build_creative / preview / VAST / DAAST\n" +
" - brand — brand.json / brand registry / hierarchy / property catalog\n" +
" - governance — sync_governance / check_governance / IO / approval flows / audit\n" +
" - sponsored-intelligence — TMP / SI sessions / context-match / identity-match\n" +
" - schema — JSON Schema source-of-truth / codegen / validation hygiene\n" +
" - compliance-suite — storyboards / conformance / certification testing\n" +
" - addie — Addie behavior / prompts / KB / chat surface / training\n" +
" - rfc — protocol change proposal that needs WG vote\n" +
" - admin-tool / website / member-tools — non-protocol surfaces\n" +
"Apply BOTH `needs-wg-review` AND at least one domain label on `ready-for-human`. Skip the WG labels if the issue is pure engineering (CI infra, deps, internal tooling) or already a confirmed bug awaiting only implementation. The label only fires the WG signal — it doesn't replace the triage comment.\n"
end) +
(if $nudge == "" then "" else $nudge + "\n" end) +
(if $comment_body == "" then "" else
Expand Down
Loading