Hi Duy, > This is a general problem to new files, not .gitignore alone. Can we
The difference, to me, is that a ".gitignore" file is not part of what I'm developing. It's an artifact for git configuration. While a .gitignore file is not always pushed to the repository, I imagine that in most situations, it is. Whereas when a "new" file is created, there are plenty of situations where it shouldn't be added and thus a warning would be superfluous, or an automatic add would be undesirable. To solve the problem, generally, for new files while giving the user the ability to specify exactly what "new" files should be automatically added to the repository, something like the following would work: echo "**/.gitignore" >> .git/config/add-before-commit > and perhaps you want to make it a habit to run it before committing. Right, because software shouldn't automate repetitive tasks and humans are never prone to forget? ;-)
