[flagged]
Also:
git status --ignored
git clean -ndX # preview what would be removed
git clean -fdX # actually delete the files (warning: destructive)And `rm ./.gitignore` will, predictably, leave the tree without a ./.gitignore (i.e., the desired state) whereas `git status --ignore`, uh, won't.
Also you can do `git status --ignored` and it will list all files changed, even if ignored. If that is really your main issue.
I don't know you think that will do or how symlinks work, but it won't lead to anything relevant to this discussion. (To answer your question: no.)
My comment and the other replies show you how to use git to check and clean the files of the much maligned horked build script. These will work regardless of the gitignore contents.
But then again, pretty sure you are just having a laugh at our expense by taking this ridiculous position.
> The symlink creates what is effectively a version-controlled gitignore
No, it doesn't—like I already said. The ln(1) invocation you wrote is not going to work. As written, it contains two glaring errors obvious on sight to anyone who actually has enough experience with the particulars of /bin/ln and Git and how repos get populated with a default .git/info/exclude.
> My comment and the other replies show you how to use git
Oh, gee, thanks!