Update git-add.js

[rozbo]

tested this way is the simplest to resolve
#2151
#1075
#2267
#2141
#2113
#1096
#216

etc....

       -u, --update
          Update the index just where it already has an entry matching <pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.     
If no <pathspec> is given when -u option is used, all tracked files in the entire working tree are updated (old versions of Git used to limit the update to the current directory and its subdirectories).

It has a flaw in that it cannot track the newly created files, but no new files are created in our scenario, so it is suitable for us.

[evocateur]

I don't see how any of the other tickets beyond the first one are related. In any case, you might have noticed from the myriad test failures that it isn't quite this simple. CHANGELOG.md might not exist, after all.

[rozbo]

Omm, it's my fault, I didn't look at the pull request notice. I am so sorry!
But as you can see, this case happens when a package to be published is in a .gitignore file. In this case, it should be logical that the check is no longer performed. but the actual situation is no difference to execution git add, this cause the error.
I really think this is a common scenario. For example, in a multi-person development scenario, a local development package doesn't want to be shared with others. At this point, obviously I should put it in gitignore. Another example is a dynamically generated package
the issues above is search the related words , it's scenario is related this problem.
In my point, the most thorough solution is to add an option to completely ignore the packages I don't want to publish, rather than relying on the private option. just like command.bootstrap.ignore.
Anyway, I wish you all the best, thank you for everything you have done!

[evocateur]

Thanks for understanding.