When would you use .git/info/exclude instead of .gitignore to exclude files? -


i bit confused pros , cons of using .git/info/exclude , .gitignore exclude files.

both of them @ level of repository/project, how differ , when should use .git/info/exclude ?

the advantage of .gitignore can checked repository itself, unlike .git/info/exclude. advantage can have multiple .gitignore files, 1 inside each directory/subdirectory directory specific ignore rules, unlike .git/info/exclude.

so, .gitignore available across clones of repository. therefore, in large teams people ignoring same kind of files example *.db, *.log. , can have more specific ignore rules because of multiple .gitignore.

.git/info/exclude available individual clones only, hence 1 person ignores in clone not available in other person's clone. example, if uses eclipse development may make sense developer add .build folder .git/info/exclude because other devs may not using eclipse.

in general, files/ignore rules have universally ignored should go in .gitignore, , otherwise files want ignore on local clone should go .git/info/exclude


Comments

Popular posts from this blog

apache - Remove .php and add trailing slash in url using htaccess not loading css -

javascript - jQuery show full size image on click -