Conversation
Let me put it the other way: I use to create my own
But I want to keep the files of the 500 IDEs I am using 😀 .
True, but I think a local |
I agree with that although I find it beneficial to have one with the repo so when you clean checkout and work on it you don't end up having to set up everything again. Your workflow is unusual as in I haven't seen it before as all projects I've worked with have a .gitignore due to the above reasoning (checkout experience) Anyway, your repo, your call ;) |
|
I have to do a bit of research on this issue. I'll leave the PR open in the meanwhile. |
Contains common files created e.g. by IDEs (build folder) and by pip (/scorep.egg-info) This avoids accidentally committing build artifacts and leads to less polluted `git status` output
Contains common files created e.g. by IDEs (build folder) and by pip (/scorep.egg-info)
This avoids accidentally committing build artifacts and leads to less polluted
git statusoutputFactored out from #68
Regarding comments:
You are not required to do this. If you are fine with
git statusshowing your IDE files you don't need to do anythingWhat mess? This is a text file and there are only some common files/folders which are recreated very frequently. The .gitignore file is meant to reduce the mess
git statusshows which will then show a clean working tree when it is clean (in terms of git)For that use case use
git clean -dfxwhich does also remove ignored files--> In summary it helps to focus on the important files especially when adding new ones