.gitignorganization

[benalleng]

From some post merge discussion I don't want to get lost. #1295 (comment) I think it would be helpful to come to a consensus on how we want to organize and document our gitignore. Though not mission critical I think a well organized gitignore can sometimes be helpful to make sense of all the generated files strewn about in a large repo.

Here are the docs in case there is some useful knowledge to be gleaned from there https://git-scm.com/docs/gitignore

Some things to consider.

• Should we have one large gitignore separated in blocks for each workspace or should each workspace have its own gitignore?
• How much documentation should we expect to explain why some files are ignored?

[nothingmuch]

i vote for separate files in subdirectories, seems more organized and easier to maintain organization as they grow

fwiw a good acceptance criteria should be that you don't have to do anything to start working with jujutsu on any part of the project

[spacebear21]

I agree with separate .gitignore files per directory. Adding explanatory comments for each line of ignore would be useful.