Based on the comment from @bertwesarg we should think about cleaning up .gitignore
This issue is for collecting argument for cleaning up .gitignore or keep the IDE specific exclusions.
I can only speak for myself but I do not configure my git environment on all systems I work with.
I use for quick tests often not configured systems where I am happy that I not see all tmp files when I run git diff to compare my current changes with the last commit.
I am against cleaning up .gitignore to keep my dirty workflows on the 7+ systems I working on.
I also cannot follow his argument.
There is a reason why GitHub provides .gitignore templates for projects, also adding the IDE files our developers use is just nice and does not harm in any way.
I can only speak for myself but I do not configure my git environment on all systems I work with.
But you do setup your editor, right?
I use for quick tests often not configured systems where I am happy that I not see all tmp files when I run
git diffto compare my current changes with the last commit.
Since when does git diff shoes you untracked files?
What exactly would we achieve doing this? Other than a .gitignore with fewer lines, that is.
As this topic was a poll and I see 3 votes for keeping the current state and only 1 for removing entries from the .gitignore, I will close this now.