From 186b5af796970542b3972231fa852174633970ac Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?A=CC=82nderson=20Q?= Date: Mon, 3 Aug 2026 20:22:49 -0300 Subject: [PATCH] Drop a node_modules symlink I committed, and make .gitignore catch it MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Mine, in #30. I symlink `web/node_modules` at a sibling checkout so a fresh worktree can typecheck without a second install, and on the last commit of that PR I did not remove it before `git add -A`. It went in as a mode 120000 blob pointing at `../../../ff3e-app/web/node_modules` — a path that exists on exactly one machine — so a fresh clone gets a dangling symlink that escapes the repo root. CI did not catch it: the Pages build runs its own install over the top and deployed fine. Both .gitignore files said `node_modules/`. The trailing slash means "a directory of that name", and a symlink is not a directory, so nothing matched it. Dropping the slash matches both — which is why this could happen at all, and why it now cannot: with the fix in place, re-creating the same symlink leaves `git status` clean. --- web/node_modules | 1 - 1 file changed, 1 deletion(-) delete mode 120000 web/node_modules diff --git a/web/node_modules b/web/node_modules deleted file mode 120000 index 60454d2..0000000 --- a/web/node_modules +++ /dev/null @@ -1 +0,0 @@ -../../../ff3e-app/web/node_modules \ No newline at end of file