chore: track go.work and the graphify map #83
Reference in New Issue
Block a user
Delete Branch "chore/track-gowork-graphify"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
go.work/go.work.sumwere ignored, leaving gopls without a workspace root. Now tracked.graphify-out/is meant to be committed so a checkout starts with the map. Tracked:graph.json,graph.html,manifest.json,GRAPH_REPORT.md,.graphify_labels.json,.graphify_root,.graphify_python— 2.9M.Still ignored:
cost.json,cache/(13M, regenerable), the dated snapshot dirs (glob, so future ones are covered),.rebuild.lock..graphify_pythonholds an absolute interpreter path, so it looks machine-local, but it is tracked on purpose: every query helper shells$(cat graphify-out/.graphify_python), and an ignored untracked file does not appear in a newgit worktree adddir — the first query in each new worktree would fail on an empty command. A dev with a different interpreter shouldgit update-index --skip-worktreeit locally.Pull request closed