Skip to content

Commit 4e45cfa

Browse files
skills(running-tend): fix diagnostic-bundle path for linked worktrees (#3479)
1 parent 3e385f4 commit 4e45cfa

1 file changed

Lines changed: 15 additions & 7 deletions

File tree

.claude/skills/running-tend/SKILL.md

Lines changed: 15 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -149,13 +149,21 @@ addressed is intentional.
149149

150150
When you need more information to diagnose a reported bug, the **primary
151151
ask is `wt -vv <command>`**. Re-running the failing command with `-vv`
152-
writes `.git/wt/logs/diagnostic.md` — a single report containing wt/git/OS
153-
versions, shell integration, `wt config show`, `git worktree list
154-
--porcelain`, and a `trace.log` of every git invocation with its output —
155-
and prints a `gh gist create --web <path>` hint. One gist URL pasted into
156-
the issue gives us most of what we'd otherwise ask for piecemeal, so lead
157-
with this for unexplained failures rather than chaining version/config/repro
158-
questions across multiple round-trips.
152+
writes a diagnostic bundle — a single report containing wt/git/OS versions,
153+
shell integration, `wt config show`, `git worktree list --porcelain`, and a
154+
`trace.log` of every git invocation with its output. The `-vv` output prints
155+
the bundle's exact absolute path (`Logs, performance profile, and
156+
diagnostics saved @ …`) followed by a ready-to-run `gh gist create --web
157+
<path>` line — **point the user at those printed lines; don't hand them a
158+
hardcoded path**. In particular, never tell them to `cat
159+
.git/wt/logs/diagnostic.md`: inside a linked worktree `.git` is a gitdir
160+
*file*, not a directory, so that path fails with `Not a directory (os error
161+
20)` (`ENOTDIR`). The bundle actually lives under the git *common* dir —
162+
`"$(git rev-parse --git-common-dir)/wt/logs/diagnostic.md"` resolves from any
163+
worktree, and the printed absolute path already points there. One gist URL
164+
pasted into the issue gives us most of what we'd otherwise ask for piecemeal,
165+
so lead with this for unexplained failures rather than chaining
166+
version/config/repro questions across multiple round-trips.
159167

160168
When the report is about a slow `wt` command, read its **Performance profile**
161169
section first. It renders the same breakdown as `wt config state logs profile`

0 commit comments

Comments
 (0)