3 ms·
Disagree. Many projects may want to commit IDE files. Ignoring them globally is simply wrong.
by forrestthewoods 2y ago
Disagree.
Many projects may want to commit IDE files. Ignoring them globally is simply wrong.
- eddiejaoude 2y agooh wow, really! why? sounds like a horrible project, imagine those git conflicts can you elaborate on why they would want to commit IDE generated files? I have only seen this in legacy projects what happens if people want to use different IDEs?
- Retr0id 2y agoIDE-specific files aren't necessarily auto-generated. They might include project-specific configs (random examples that come to mind include linter configs, tab/space indent settings, C library include paths)
- S04dKHzrKT 2y agoJetbrains' .DotSettings file is a specific example. It contains things like project specific dictionaries for the IDE's spell checker.
- forrestthewoods 2y ago> imagine those git conflicts Not an issue > why they would want to commit IDE generated files You added the word generated. Many Windows-oriented projects a Visual Studio .sln file. This is great! You can open the sln, build, and run. It “just works”. Very nice. I wish more projects did this. > what happens if people want to use different IDEs? That’s fine. Nothing stopping it.
- WCSTombs 2y agoOnce they're committed into the repository, they're no longer ignored, so what's the problem? The IDE files being listed in a hypothetical developer's global .gitignore do no harm in this case.
- forrestthewoods 2y agoI utterly fucking despise that Git allows ignored files in some cases. FUCKING DESPISE. IMHO the .gitignore should be the source of truth.