Hi again, It has been pointed out to me that some developers chose to locally alter the .gitignore file to add custom exclusion rules for their environment. This would result in .gitignore being listed as modified when running the git status command.
One proposition is to add .gitignore to itself. This would allow developers to update the file without worrying about sharing their custom .gitignore file with the rest of the development community in one of their commits. However, their is a drawback in doing so. There is no guarantee that the current version of the .gitignore file will remain as it is currently. One realistic scenario I’ve heard is “What if we were to support another build tool and we wanted to ignore the files it generates?” Having .gitignore exclude itself is not the best option. Another proposition is to store custom exclusions in the .git/info/exclude file. This is actually the better alternative. The .git/info/exclude was designed to store exclusions outside of the tree. Moreover, these custom rules are only applied to your checked out version of the repository and will never be included when committing. We have opted to go with the second proposition. Developers need to use the .git/info/exclude file for custom exclusion rules. I will be committing the .gitignore file to the project today. Regards, François On May 7, 2014, at 10:42 AM, Francois Caron <[email protected]> wrote: > Hi, > > A .gitignore file should accompany the project instead of having each > developer create his own. > > The following should work for now. I’ll add it in my next commit. > > François > > <gitignore> -- To unsubscribe visit http://f265.org or send a mail to [email protected].
