I made a small utility for listing the file names inside an archive file, e.g. tar, zip, etc. This comes in handy when you download some software package using the command line but you aren't sure whether to extract it in its own folder because you don't know what the file structure inside is.

you are viewing a single comment's thread
view the rest of the comments
[+] 0 points 1 year ago (7 children)
  • [–] 1 point 1 year ago (4 children)

    How is it not part of the project?

  • source
  • parent
  • hideshow 4 child comments
  • [+] 0 points 1 year ago (3 children)
  • [–] 2 points 1 year ago (2 children)

    So everyone who contributes to the project should make their own gitignore on every development machine they use to prevent committing build files, secrets ect?

    I don't understand why you say it has nothing to do with the code when it literally has nothing to do with anything BUT the code.

    What is the downside you see to committing the gitignore?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 year ago*

    You never want build artifacts to be committed. You don't want to have everyone working on your project to need to setup their own gitignore for every project. So it makes sense to have a common commited gitignore for files the project produces that should never be tracked by git.

    I dislike when people put in editor files in the gitignore though. People should setup global ones for their local tooling.

  • source
  • parent