The best way to control Claude Code, Codex and more from any computer or phone
fix(triage): file labeled reports through the issue template (#31321)
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Ilkka Lappeteläinen committed
Nov 19, 2026 at 22:03 UTC
1e9f4c45c3c143c4f405d47d250b649f82c5d656
2 files changed
+28
-6
.github/triage/PLAYBOOK.md
+14
-3
@@ -125,9 +125,20 @@ of `main` for that work, never the tag-pinned diagnosis clone.
125
- Show the user the complete final issue text and get an explicit yes before
126
posting. Never post without it.
127
- Note at the end of the issue which model and agent produced it.
128
-- Post with `gh issue create --repo pingdotgg/t3code --label via-triage` only
129
- if `gh api repos/pingdotgg/t3code --jq .permissions.triage` prints `true`.
130
-- Otherwise, or if `gh` is not authenticated, build a prefilled
128
+- If `gh` is authenticated to github.com, post through the "Triage report"
129
+ issue template. It applies `via-triage` for every reporter, while
130
+ `gh issue create --label` drops the label without triage permission. Write
131
+ the approved title and body to files, the title without a trailing newline,
132
+ so the shell never parses their text. Then run:
133
+
134
+ gh api --hostname github.com graphql -f repo="$(gh api --hostname github.com repos/pingdotgg/t3code --jq .node_id)" -f template="Triage report" -F title=@<title-file> -F body=@<body-file> -f query='mutation($repo:ID!,$template:String!,$title:String!,$body:String!){createIssue(input:{repositoryId:$repo,issueTemplate:$template,title:$title,body:$body}){issue{url labels(first:20){nodes{name}}}}}'
135
+
136
+ Report the issue URL and whether its labels include `via-triage`. Never file a
137
+ second issue to repair a label. If you cannot tell whether the issue was
138
+ created, check the user's recent issues before you retry.
139
+
140
+- If `gh` is not authenticated, or the request was rejected and created
141
+ nothing, build a prefilled
142
https://github.com/pingdotgg/t3code/issues/new?template=via-triage.yml URL.
143
The form applies the label whoever submits it. Add `title` plus one
144
URL-encoded query parameter per form field id: `what-happened`, `diagnosis`,
apps/server/src/triage/triagePrompt.ts
+14
-3
@@ -129,9 +129,20 @@ of \`main\` for that work, never the tag-pinned diagnosis clone.
129
- Show the user the complete final issue text and get an explicit yes before
130
posting. Never post without it.
131
- Note at the end of the issue which model and agent produced it.
132
-- Post with \`gh issue create --repo pingdotgg/t3code --label via-triage\` only
133
- if \`gh api repos/pingdotgg/t3code --jq .permissions.triage\` prints \`true\`.
134
-- Otherwise, or if \`gh\` is not authenticated, build a prefilled
132
+- If \`gh\` is authenticated to github.com, post through the "Triage report"
133
+ issue template. It applies \`via-triage\` for every reporter, while
134
+ \`gh issue create --label\` drops the label without triage permission. Write
135
+ the approved title and body to files, the title without a trailing newline,
136
+ so the shell never parses their text. Then run:
137
+
138
+ gh api --hostname github.com graphql -f repo="$(gh api --hostname github.com repos/pingdotgg/t3code --jq .node_id)" -f template="Triage report" -F title=@<title-file> -F body=@<body-file> -f query='mutation($repo:ID!,$template:String!,$title:String!,$body:String!){createIssue(input:{repositoryId:$repo,issueTemplate:$template,title:$title,body:$body}){issue{url labels(first:20){nodes{name}}}}}'
139
+
140
+ Report the issue URL and whether its labels include \`via-triage\`. Never file a
141
+ second issue to repair a label. If you cannot tell whether the issue was
142
+ created, check the user's recent issues before you retry.
143
+
144
+- If \`gh\` is not authenticated, or the request was rejected and created
145
+ nothing, build a prefilled
146
https://github.com/pingdotgg/t3code/issues/new?template=via-triage.yml URL.
147
The form applies the label whoever submits it. Add \`title\` plus one
148
URL-encoded query parameter per form field id: \`what-happened\`, \`diagnosis\`,