3 ms·
You still want to put these kinds of things in every project where you are collaborating. You can't depend on everyone to know and do this, so best to just be p
by jmholla 8mo ago
You still want to put these kinds of things in every project where you are collaborating. You can't depend on everyone to know and do this, so best to just be prepared for those who don't.
- Defletter 8mo agoI have this two liner as part of my post-os-install setup script: curl -fsSL https://www.toptal.com/developers/gitignore/api/linux > ~/.gitignore git config --global core.excludesFile ~/.gitignore
- phyzome 8mo agoI'd prefer to leave them out. That way I can see who's not paying attention when they make commits and are just doing `git commit -a -m "yolo"`.
- saila 8mo agoSurely you'll be able to tell who's YOLOing commits without allowing junk into your repo that you'll have to clean up (and it almost certainly be you doing it, not that other person). DS_Store files are just annoying, but I've seen whole bin and obj directories, various IDE directories, and all kinds of other stuff committed by people who only know git basics. I've spent way more effort over time cleaning up than I have on adding a comprehensive gitignore file. It takes practically no effort to include common exclude patterns and avoid all that. Personally, I just grab a gitignore file from GitHub and make a few tweaks here and there: https://github.com/github/gitignore/ https://github.com/github/gitignore/
- socalgal2 8mo agoI prefer to leave them in. Why waste my time reviewing PRs that would have been fin otherwise. And, why waste other people's time.