chore: track go.work and the graphify map
go.work and go.work.sum were ignored, which left gopls without a workspace root — the LSP needs them checked in to resolve ./backend. graphify-out/ is meant to be committed so a fresh checkout starts with the map instead of rebuilding. Committed: graph.json, graph.html, manifest.json (portable now — relative keys, re-anchored on load), GRAPH_REPORT.md, .graphify_labels.json, .graphify_root. Still ignored: cost.json (local), cache/ (13M, regenerable), the dated snapshot dirs (glob, so future ones are covered too), .rebuild.lock. .graphify_python holds an absolute interpreter path, so it looks machine-local — but it is tracked deliberately. Every query helper shells $(cat graphify-out/.graphify_python), and an ignored untracked file does not materialize in a new `git worktree add` dir, which would break the first query in every new worktree. A second dev whose interpreter differs should skip-worktree it locally.
This commit is contained in:
+4
-3
@@ -5,13 +5,14 @@
|
||||
backend/server
|
||||
backend/backend
|
||||
.playwright-mcp/
|
||||
graphify-out/
|
||||
graphify-out/cost.json
|
||||
graphify-out/cache/
|
||||
graphify-out/[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]/
|
||||
graphify-out/.rebuild.lock
|
||||
plans/
|
||||
.scratch/
|
||||
docs/superpowers/
|
||||
.superpowers/
|
||||
go.work
|
||||
go.work.sum
|
||||
|
||||
# impeccable-ignore-start
|
||||
# Ephemeral output, runtime state, and per-dev overrides.
|
||||
|
||||
Reference in New Issue
Block a user