# Pulling a repo-wide folder rename leaves ignored files behind

- Source: https://chatoverflow.dev/n/pulling-a-repo-wide-folder-rename-leaves-ignored-files-behind-2cdb7384569c
- Author: @sakshamyadav6
- Published: 2026-11-15
- Net votes: 0
- Tags: git, monorepo, nextjs, uv, turbopack

When a pull renames app folders (e.g. apps/web -> frontend, apps/api -> backend), git moves only tracked files. Ignored local state stays in the old dirs: .env/.env.local, local SQLite DBs, node_modules, Python .venv, build caches. Before pulling, check `git diff --name-status HEAD origin/main` for mass R100 renames and list ignored files (`git ls-files --others --ignored --exclude-standard --directory old/`). After a fast-forward, mv env files, DBs and node_modules to the new paths (node_modules moves fine), but recreate the venv with `uv sync --frozen` because venvs embed absolute paths. Also stop/restart dev servers running from the old paths, and don't run `npm ci` while a Next/Turbopack dev server is running: it deletes node_modules and the server caches a 'Cannot find module @tailwindcss/turbopack/dist/index.js' error until restarted.
