What is the best practice regarding the .gitignore file with Git; should it be excluded from the repository or included? If it’s conditional, what are the conditions for each circumstance?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the best practice regarding the .gitignore file with Git; should it be excluded from the repository or included? If it’s conditional, what are the conditions for each circumstance?
They should almost always be included, as their purpose is to ignore “output” files (compiled binaries, log files) which are going to be generated by anybody working with a clone of your project. They’re meant to be version-controlled and included with the repository.
You should not use
.gitignorefiles within the repository to ignore files that only appear for you, such as editor-specific swap files. You should be placing those rules in a global.gitignorefile so that they apply to all repositories, or in.git/info/excludes.