Re:Don't include configs in your Git repos
by jamiewildehk on Wednesday October 28, 2015 @11:49PM
(#10469163)
Ahh, but do you then commit your .gitignore file
[ Parent
| on HN ]
Re:Don't include configs in your Git repos
by twblalock on Thursday October 29, 2015 @12:58AM
(#10469366)
I always do. My company has a canonical .gitignore that we update when we see things in git repos that should not be there. It now contains all of the stupid hidden project directories for all of the major IDEs, build artifacts we don't want, and a bunch of other stuff.
I highly recommend this approach.
Re:Don't include configs in your Git repos
by deathanatos on Thursday October 29, 2015 @12:51AM
(#10469341)
Absolutely. .gitignore is a project-level declaration that "these files do not belong in source control". Keeping that in source control not only makes sure everyone gets the same copy, but also allows changes to be annotated by relevant commit messages.
Re:Don't include configs in your Git repos
by dvanduzer on Wednesday October 28, 2015 @11:54PM
(#10469178)
Subtle.
Re:Don't include configs in your Git repos
by krapp on Wednesday October 28, 2015 @11:55PM
(#10469181)
yes?
Re:Don't include configs in your Git repos
by jamiewildehk on Thursday October 29, 2015 @12:25AM
(#10469261)
For our internal projects here we do - it saves is hassle of someone accidentally committing /node_modules or the like into the repo and someone (me) having to sort it out.