Merging in latest from upstream (GEN/boilerplate-project-npm:refs/heads/develop)* commit 'f6f7afa36017be6e97bf9c6e03055c4828daac32':
chore(project): make `npm`'s default version-range a more conservative one
Merging in latest from upstream (GEN/boilerplate-project:refs/heads/develop)* commit 'da1422647b8022c9592c41f4c2ead902464cb8a1':
chore(project): ignore stuff _in_ directories instead of directories per se
chore(project): update ignore patterns
chore(project): empty `package-lock.json` to simplify after-fork steps for new forks of this repoMerges of this newer change into existing forks should simply select "--ours" (from "their" perspective) to resolve the conflict;
Merging in latest from upstream (GEN/boilerplate-project:refs/heads/develop)* commit 'eeec7ec5314ed34ab5ef3bca148e6a4c6f111495':
chore(project): add more exclusions
Merging in latest from upstream (GEN/boilerplate-project:refs/heads/develop)* commit '8a99f62714cddaa013f3c9d804fab2239b88db10':
chore(project): whitelist (unignore) README's in blacklisted directories
chore(project): whitelist (unignore) README's in blacklisted directories - Whitelisting is better done after blacklisting;
- Will only work if directories are blacklisted as `<directory>/*`;
See: https://git-scm.com/docs/gitignore#_pattern_format
> It is not possible to re-include a file if a parent directory of that file is excluded. Git doesn’t list excluded directories for performance reasons, so any patterns on contained files have no effect, no matte...
Merging in latest from upstream (GEN/boilerplate-project:refs/heads/develop)* commit 'ac1e4515ff78920083c1566c71fc2142868142b8':
chore(project): whitelist (unignore) README's in blacklisted trees
Merging in latest from upstream (GEN/boilerplate-project:refs/heads/develop)* commit 'b34bfd42e562d64d88f12a1aac403616a949bf0f':
chore(project): additionally `.giignore` various archive files
David Bouman