From 581e29e23784f34f59b48e8ae235298a3aaf3d2f Mon Sep 17 00:00:00 2001 From: hyperpolymath <6759885+hyperpolymath@users.noreply.github.com> Date: Mon, 18 May 2026 11:06:11 +0100 Subject: [PATCH] chore: gitignore package-lock.json (mirror Cargo.lock policy) vscode-extension/package-lock.json was untracked but not ignored, so it permanently showed in `git status` and risked accidental staging. This repo already deliberately gitignores Cargo.lock; apply the same lockfile policy to the npm side (the only such file is the vscode extension's). Co-Authored-By: Claude Opus 4.7 (1M context) --- .gitignore | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.gitignore b/.gitignore index 67747ae..11685a7 100644 --- a/.gitignore +++ b/.gitignore @@ -37,6 +37,9 @@ Thumbs.db *.log target/ node_modules/ +# npm lockfile — not tracked, mirroring the Cargo.lock policy above +# (the only one is vscode-extension/package-lock.json) +package-lock.json _build/ deps/ .elixir_ls/