Skip to content

Commit 6b97494

Browse files
fix(triage): file reports through the issue form so via-triage sticks
`gh issue create --label via-triage` drops the label without a word unless the account has triage or write permission, and the documented fallback URL selects no template, so it applies none of via-triage.yml's labels either. Check the permission first, and file through `?template=via-triage.yml` when it is absent. Fixes #8061 Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01MP4xv7WtAw6hteCNMu7cfn
1 parent fff33f9 commit 6b97494

2 files changed

Lines changed: 26 additions & 10 deletions

File tree

‎.github/triage/PLAYBOOK.md‎

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -104,14 +104,22 @@ of `main` for that work, never the tag-pinned diagnosis clone.
104104
- Match the structure of the `via-triage` issue template
105105
(`.github/ISSUE_TEMPLATE/via-triage.yml` in the repo): what happened, diagnosis,
106106
repro steps, environment, evidence, related issues.
107-
- Label it `via-triage`. Use a plain, specific title with no prefix.
107+
- Use a plain, specific title with no prefix.
108+
- The issue needs the `via-triage` label. `gh issue create --label via-triage`
109+
drops it silently unless the account has triage or write permission; check with
110+
`gh api repos/pingdotgg/t3code --jq .permissions.triage` before posting.
111+
- Without that permission, file through the issue form: it carries the template's
112+
label whoever submits. Build `issues/new?template=via-triage.yml` with `&title=`
113+
and one `&<field-id>=` per field in `via-triage.yml`, url-encoded. Never pass
114+
`labels`; GitHub answers 404 when the reader cannot apply it.
115+
- When the report is too long to prefill in a URL, open the bare
116+
`issues/new?template=via-triage.yml` form and have the user paste the approved
117+
text into the fields. That path needs no `gh` and still carries the label.
108118
- Show the user the complete final issue text and get an explicit yes before
109119
posting. Never post without it.
110120
- Note at the end of the issue which model and agent produced it.
111-
- If `gh` is not authenticated, offer `gh auth login`, or build a prefilled
112-
https://github.com/pingdotgg/t3code/issues/new URL with title and body query
113-
parameters; print the URL, and open it in their browser only after they
114-
approve.
121+
- If `gh` is not authenticated, offer `gh auth login`, or fall back to the issue
122+
form; print the URL, and open it in their browser only after they approve.
115123
- If the user pasted screenshots, remind them to drag the images into the issue
116124
after it is created; they cannot be attached from here.
117125

‎apps/server/src/cli/triagePrompt.ts‎

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -116,14 +116,22 @@ of \`main\` for that work, never the tag-pinned diagnosis clone.
116116
- Match the structure of the \`via-triage\` issue template
117117
(\`.github/ISSUE_TEMPLATE/via-triage.yml\` in the repo): what happened, diagnosis,
118118
repro steps, environment, evidence, related issues.
119-
- Label it \`via-triage\`. Use a plain, specific title with no prefix.
119+
- Use a plain, specific title with no prefix.
120+
- The issue needs the \`via-triage\` label. \`gh issue create --label via-triage\`
121+
drops it silently unless the account has triage or write permission; check with
122+
\`gh api repos/pingdotgg/t3code --jq .permissions.triage\` before posting.
123+
- Without that permission, file through the issue form: it carries the template's
124+
label whoever submits. Build \`issues/new?template=via-triage.yml\` with \`&title=\`
125+
and one \`&<field-id>=\` per field in \`via-triage.yml\`, url-encoded. Never pass
126+
\`labels\`; GitHub answers 404 when the reader cannot apply it.
127+
- When the report is too long to prefill in a URL, open the bare
128+
\`issues/new?template=via-triage.yml\` form and have the user paste the approved
129+
text into the fields. That path needs no \`gh\` and still carries the label.
120130
- Show the user the complete final issue text and get an explicit yes before
121131
posting. Never post without it.
122132
- Note at the end of the issue which model and agent produced it.
123-
- If \`gh\` is not authenticated, offer \`gh auth login\`, or build a prefilled
124-
https://github.com/pingdotgg/t3code/issues/new URL with title and body query
125-
parameters; print the URL, and open it in their browser only after they
126-
approve.
133+
- If \`gh\` is not authenticated, offer \`gh auth login\`, or fall back to the issue
134+
form; print the URL, and open it in their browser only after they approve.
127135
- If the user pasted screenshots, remind them to drag the images into the issue
128136
after it is created; they cannot be attached from here.
129137

0 commit comments

Comments
 (0)