6 ms·
I'd rather enforce it at the repo then hope and pray everyone updates their global configs. Easy enough to catch but you'll miss some. Literally no cost to add
by wobblyasp 2y ago
I'd rather enforce it at the repo then hope and pray everyone updates their global configs.
Easy enough to catch but you'll miss some. Literally no cost to adding it to repo config either
- eddiejaoude 2y agoyes as an open source maintainer, this is a difficult decision I need to make for each project. On one hand, I want to do the right thing, but on the other, the initial convenience does come into play - but this can come back to bite us later when people play the green square game on the git ignore file in the GitHub repo