I want to move a typescript file in VSCode such that:
I can achieve either, but not both.
Using git mv: VSCode doesn't update the parent files' import statements.
Using manual drag & drop: git regards this as a new file.
How can I do both?
After doing more research, it turns out git does not actually track file renames.
Compare:
After using git mv, your git status will return something like:
renamed: someFileName.ts -> newFileName.ts
After using mv, your git status will return something like:
deleted: someFileName.ts
untracked: newFileName.ts
^despite the apparent acknowledgement of a rename, git handles both scenarios identically.
After running git add -- someFileName.ts newFileName.ts, you will get the same:
renamed: someFileName.ts -> newFileName.ts
Interestingly, this is not the norm for most SCMs. Linus explains the design decision here.
So to answer the original question: Use the VSCode integrated file explorer for file moves/renames - this updates import paths AND there is no detriment to version control.
git log newFileName.ts in each case?
git log newFileName.ts will stop at the first commit, but git log --follow newFileName.ts will also follow the history of someFileName.ts.git mv old new is just a shortcut for git rm --cached old; mv old new; git add new (it is a bit more elaborate because it also preserves "staged content" and "worktree content", but that's the gist of it)