I had to do some work in an older C# repo. I see git is automatically ignoring each new class I add. After scouring the .gitignore file, I see this entry put in by one of my colleagues.

Close-Open principle.

Closed for additions, Open for modifications.

The software is perfect as it is. Adding things will just mar the perfection that currently exists. (/S)

I don't think I've ever seen a gitignore that was more than 70 lines, much less 247+ wowee

@ElectroMantis this VS solution is a legacy monolith with 196 projects in it.

Ay Caramba

That's one hell of a gitignore

@powerfulparadox I unsarcastically believe that there is a point for many products where this is true, and it's much earlier in the development process than most product managers think it is.

@duckWit F

trolololololol

@halfflat well you do want to ignore your dev .env filea

@bittersweet I agree, but this is not the proper way to enforce that.

@Mr-Myrk or build targets, or cache related files. I don’t think they quite understand it

@Plasticnova oh which reminds me, also IDE files, dependencies etc

@ElectroMantis Depending on the Build environment (IDE, Build Tools etc.) and the selected language(s) the gitignore might grow fastly. Have a look at the gitignore Repo at GitHub. There are some quite long gitignores. And maybe it also has some comments, empty lines etc.

@halfflat windows is the dirtiest development environment. I’m dealing with fallout from people not putting gitignores in vs projects. Holy shit it’s a ton of useless files