21–30 of 72 posts
Disagree. Many projects may want to commit IDE files. Ignoring them globally is simply wrong.
oh 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?
Disagree. Many projects may want to commit IDE files. Ignoring them globally is simply wrong.
Everyone is free to pick a proverbial hill to die on. Some focus on battles they are likely to win, others on battles they are bound to lose.
Earlier quoted context omitted.
yes exactly! then we end up with every IDE, operating system and dev tools (which is a lot)
Why is it a problem to have a long .gitignore?
And to find the answer to “why is it a problem that there's a .sublimetext line in the .gitignore” then ask yourself the question “why is it a problem if there's a .sublimetext file committed to the repository”. Why even bothering to add it to the .gitignore when you can just commit the file?
Why do you think the second scenario is an issue and not the first?
This seems like a terrible idea.. imagine framework A that has a throwaway folder called ".blah"—now imagine framework B that has a very important configuration folder called ".blah"—so at best this would only cover IDE and OS stuff. But that stuff ends up being like what, 10 lines at most?
Being honest, I dislike the tone of this sort of clickbaity rephrasing of the article title. The actual title is "You must use your Global Git Ignore!" which is completely true; the nuanced observation from the article "Using the git ignore feature is great but it has limitations, which is why I think this file is overused and often incorrectly" is a worthwhile hook, and presented thoughtfully. The title "Stop Using…
Thank you for the detailed feedback, I really appreciate you taking the time and effort. Yes the title is a little bit controversial
Earlier quoted context omitted.
Yeah, people putting MacOS-specific files that have no relation to the codebase in the .gitignore should stop.
I'm not sure about that. We had a new hire once add a ton of .DS_Store files because we forgot to ignore it at the repo level and they didn't have a global ignore set up. I don't see the point of committing files that have no purpose in the repo, especially these ones, that could change between users age potentially polluting the diffs. We added it to the ignore list and removed the files
And you could have used the opportunity to teach them about using a version control altogether and how it they aren't supposed to just throw git commit -am "fix stuff" at every problem!
The fact that they committed the .DS_store files shows there's a much deeper problem with how this employee works that something you can work around with a .gitignore file. Now the problem has just been hidden under the rug.