@@ -6,7 +6,7 @@ crashes, auth failures, broken setups, slow launches, or anything else. Your job
66find out what went wrong, unblock the user if you can, and turn what you learned into
77a well written GitHub issue when one is warranted.
88
9- A triage context file with machine facts (version , OS, paths, server liveness) was
9+ A triage context file with machine facts (versions , OS, paths, server liveness) was
1010provided alongside this playbook. Everything machine-specific lives there, not here.
1111
1212## 1. Ask what went wrong
@@ -18,9 +18,15 @@ valuable thing you can extract from this conversation.
1818
1919## 2. Read the machine facts
2020
21- Read the triage context file before investigating. It tells you the installed
22- version, the OS, whether the server process is currently running, and the exact
23- paths for state, logs, and the database.
21+ Read the triage context file before investigating. It tells you the OS, whether
22+ the server process is currently running, and the exact paths for state, logs, and
23+ the database.
24+
25+ Its triage CLI version (called "Installed version" in older context files) is only
26+ the version of the ` t3 ` that ran ` t3 triage ` . It is often not the build the bug
27+ happened on: ` npx t3 triage ` runs whatever ` t3 ` npm resolves, while the user may
28+ run the desktop app, the background service, or a nightly. The server process line
29+ gives the local server's version when the server recorded one.
2430
2531## 3. Check for a newer playbook
2632
@@ -30,8 +36,16 @@ instead of this one. The user may be on an old release with an old copy.
3036
3137## 4. Get the source
3238
33- Clone the repo at the tag matching the user's installed version, into the source
34- cache directory named in the context file, one subdirectory per commit hash:
39+ Before cloning, ask the user which version, device, and surface the bug happened
40+ on. The bug may have happened on another machine, a remote server, the mobile app,
41+ or an older build they have since updated. Check their answer against local facts
42+ where they apply: the server version in the context file, or ` serverVersion ` from
43+ ` <origin>/.well-known/t3/environment ` when a local server is running. If neither
44+ the user nor the machine can tell you the version, say it is unknown. Do not guess.
45+
46+ Clone the repo at the release tag for that version (` v ` followed by the version,
47+ such as ` v0.0.42 ` ), into the source cache directory named in the context file,
48+ one subdirectory per commit hash:
3549
3650 git clone --depth 1 --filter=blob:none --branch <release-tag> \
3751 https://github.com/pingdotgg/t3code <source-cache-dir>/<hash>
@@ -82,8 +96,8 @@ comes from this repo's `main` branch.
8296
8397Search existing issues in pingdotgg/t3code (use ` gh ` , or the public GitHub search
8498API if ` gh ` is missing or not logged in). Then check whether the problem is already
85- fixed in a release newer than the user's version: compare versions, read release
86- notes and recent commits touching the relevant code.
99+ fixed in a release newer than the version the bug happened on : compare versions,
100+ read release notes and recent commits touching the relevant code.
87101
88102If the user is behind and the fix likely shipped, say so plainly and give them the
89103exact update command for how they run the CLI (the context file records how it was
@@ -105,6 +119,8 @@ of `main` for that work, never the tag-pinned diagnosis clone.
105119- Match the structure of the ` via-triage ` issue template
106120 (` .github/ISSUE_TEMPLATE/via-triage.yml ` in the repo): what happened, diagnosis,
107121 repro steps, environment, evidence, related issues.
122+ - Under Version, give the version the bug happened on from step 4, or say it is
123+ unknown. Name the triage CLI version only as the CLI's.
108124- Label it ` via-triage ` . Use a plain, specific title with no prefix.
109125- Show the user the complete final issue text and get an explicit yes before
110126 posting. Never post without it.
0 commit comments