feat: implement issue assignment agentic workflow (go:yes trigger)#186
Merged
Conversation
Rewrite squad-issue-assign.yml to implement the go:yes label-triggered
assignment workflow:
- Trigger: issues labeled with go:yes (names filtering)
- Assigns issue to the maintainer who applied the label (sender)
- Reads prior triage analysis comment and .squad/routing.md
- Applies squad label + matched squad:{member} labels
- Safe outputs: assign-to-user max:1, add-labels allowed:[squad, squad:*]
blocked:[go:*, priority:*, override:*, type:*] max:5, add-comment max:1
- Post-check job verifies assignee == sender and all squad:{member}
labels exist in routing.md
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Move the Routing Table and Issue Routing markdown tables from .squad/routing.md into dedicated JSON files: - .squad/routing-table.json (workType, routeTo, examples array) - .squad/issue-routing.json (label, action, who) routing.md now references these JSON files. The squad-issue-assign workflow reads JSON directly instead of parsing markdown tables, resulting in much simpler and more reliable code. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Document what the agent MUST NOT do: no assignee override, no blocked label patterns, no issue mutations, no external calls, no permission escalation, no skipping post-check. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Parse .squad/routing-table.json and .squad/issue-routing.json and append structured entries to routingContent so the triage workflow has full routing information available for analysis. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Remove the squad-triage workflow that auto-triaged on the 'squad' label. The issue assignment workflow now requires maintainers to explicitly apply 'go:yes' to approve and assign issues, enforcing human-in-the-loop approval before any routing happens. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
v8 runs on Node.js 24 with no breaking API changes to the github/core context objects used in our scripts. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR replaces the prior label-driven triage/assignment automation with a maintainer-approved issue assignment workflow triggered by the go:yes label, and moves routing data into machine-readable JSON under .squad/.
Changes:
- Rewrites
.github/workflows/squad-issue-assign.ymlto deterministically assign issues to thego:yeslabel sender and apply up to 5 safe squad labels based on routing rules. - Deletes the legacy
.github/workflows/squad-triage.ymlworkflow. - Introduces
.squad/routing-table.jsonand.squad/issue-routing.jsonand updates.squad/routing.mdto reference them.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 7 comments.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/squad-issue-assign.yml |
New go:yes-triggered agentic assignment + routing + post-check logic (actions/github-script v8). |
.github/workflows/squad-triage.yml |
Removes the previous automatic triage workflow. |
.squad/routing-table.json |
Adds structured “work type → routeTo + keywords” routing data. |
.squad/issue-routing.json |
Adds structured “label → action + who” routing data. |
.squad/routing.md |
Switches routing docs to reference the new JSON sources. |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
EMaher
commented
Jun 23, 2026
Contributor
Author
|
@copilot - have the Squad handle the comments. |
azaslonov
approved these changes
Jun 23, 2026
Contributor
Author
|
Related to #90 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
The existing
squad-issue-assignworkflow triggered onsquad:{member}labels and auto-triaged via a separatesquad-triageworkflow. This bypassed human approval -- any label application could assign work. We need a deliberate, maintainer-gated entry point for issue assignment.Approach
Rewrote
squad-issue-assign.ymlas an agentic workflow triggered by thego:yeslabel:go:yes(the event sender) -- the agent never picks the assignee..squad/routing-table.jsonand.squad/issue-routing.json(new structured files) plus the prior triage comment to determine which squad areas the issue touches.assign-to-user: max 1 (sender only)add-labels: allowed[squad, squad:*], blocked[go:*, priority:*, override:*, type:*], max 5add-comment: max 1 (assignment rationale)squad:{member}labels exist in routing data. Workflow fails on mismatch.Other changes
.squad/routing-table.jsonand.squad/issue-routing.jsonfor simpler, more reliable parsing.routing.mdnow references these files.squad-triage.yml-- thego:yeslabel is now the only entry point, enforcing human-in-the-loop approval.actions/github-scriptfrom v7 to v8 (Node.js 24).Files
.github/workflows/squad-issue-assign.yml.github/workflows/squad-triage.yml.squad/routing-table.json.squad/issue-routing.json.squad/routing.md