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.

  • 26
    Close-Open principle.

    Closed for additions, Open for modifications.
  • 14
    The software is perfect as it is. Adding things will just mar the perfection that currently exists. (/S)
  • 15
    I don't think I've ever seen a gitignore that was more than 70 lines, much less 247+ wowee
  • 10
    @ElectroMantis this VS solution is a legacy monolith with 196 projects in it.
  • 2
    Ay Caramba
  • 3
    That's one hell of a gitignore
  • 3
    @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.
  • 1
  • 1
  • 1
    @halfflat well you do want to ignore your dev .env filea
  • 1
    @bittersweet I agree, but this is not the proper way to enforce that.
  • 1
    @Mr-Myrk or build targets, or cache related files. I don’t think they quite understand it
  • 3
    @Plasticnova oh which reminds me, also IDE files, dependencies etc
  • 1
    @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.
  • 1
    @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
Add Comment