55
๐Ÿง TIL: global .gitignore (dandean.com)
submitted 9 months ago by to c/programming@programming.dev
23 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[+] [S] 13 points 9 months ago (3 children)
[deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [โ€“] 5 points 9 months ago (1 child)

    I have the same preference for personal projects, but when I was working on a corporate team it was really useful to have the "run configs" for intellij checked in so that each new team member didn't need to set them up by themselves. Some of the setup needed to get the python debugger properly connected to the project could get quite gnarly.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [โ€“] 2 points 9 months ago

    Gitignore settings don't prevent checking in run configs if that's what you want to do. Even if someone has the run configs pattern ignored, they'll get those files with the repo clone. Gitignore only prevents adding files that aren't already checked in - it's a guard rail to prevent accidentally checking in so something you don't want. You can override ignore settings to check in something new in with git add --force <filename>

  • permalink
  • fedilink
  • source
  • parent
  • [โ€“] 8 points 9 months ago

    shrug To each their own, I guess.

    I can definitely appreciate that opinion, I just... disagree. I don't really give 2 shits about a file having some stuff in it that I don't personally use, so long as it still has a purpose. I.E. I'll take a little clutter in a file like that, that basically never gets looked at or edited, over the chance of cluttering up the repo itself, or PRs, or history with stuff that has no purpose at all.

  • permalink
  • fedilink
  • source
  • parent