The best way to control Claude Code, Codex and more from any computer or phone
fix(cli): t3 triage issues get the via-triage label for every reporter (#24955)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: maria-rcks <maria@kuuro.net>
Victor Vogel committed
Oct 31, 2026 at 03:34 UTC
640c614fc2465ffa2a300002dde3e863402d7e1f
2 files changed
+20
-8
.github/triage/PLAYBOOK.md
+10
-4
@@ -125,10 +125,16 @@ 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
-- If `gh` is not authenticated, offer `gh auth login`, or build a prefilled
129
- https://github.com/pingdotgg/t3code/issues/new URL with title and body query
130
- parameters; print the URL, and open it in their browser only after they
131
- approve.
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
131
+ https://github.com/pingdotgg/t3code/issues/new?template=via-triage.yml URL.
132
+ The form applies the label whoever submits it. Add `title` plus one
133
+ URL-encoded query parameter per form field id: `what-happened`, `diagnosis`,
134
+ `steps`, `version`, `environment`, `evidence`, `related`, `workaround` and
135
+ `agent`. Keep the full encoded URL below 6,000 characters by shortening any
136
+ fields as needed. Give the user any omitted text to paste into the form before
137
+ submitting. Print the URL, and open it in their browser only after they approve.
138
- If the user pasted screenshots, remind them to drag the images into the issue
139
after it is created; they cannot be attached from here.
140
apps/server/src/triage/triagePrompt.ts
+10
-4
@@ -129,10 +129,16 @@ 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
-- If \`gh\` is not authenticated, offer \`gh auth login\`, or build a prefilled
133
- https://github.com/pingdotgg/t3code/issues/new URL with title and body query
134
- parameters; print the URL, and open it in their browser only after they
135
- approve.
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
135
+ https://github.com/pingdotgg/t3code/issues/new?template=via-triage.yml URL.
136
+ The form applies the label whoever submits it. Add \`title\` plus one
137
+ URL-encoded query parameter per form field id: \`what-happened\`, \`diagnosis\`,
138
+ \`steps\`, \`version\`, \`environment\`, \`evidence\`, \`related\`, \`workaround\` and
139
+ \`agent\`. Keep the full encoded URL below 6,000 characters by shortening any
140
+ fields as needed. Give the user any omitted text to paste into the form before
141
+ submitting. Print the URL, and open it in their browser only after they approve.
142
- If the user pasted screenshots, remind them to drag the images into the issue
143
after it is created; they cannot be attached from here.
144