Template .gitignore — round 2 #698
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
When embark is installed via npm, the templates'
.gitignorefiles (which make it into the pkg tarball by way of the negation included in embark's.npmignore, owing to #694) are auto-renamed to.npmignore. This npm behavior cannot be remedied, it seems, by including empty.npmignorefiles in the template directories.So, this PR uses a different approach: template directories have a file named
dot.gitignoreand during template installation (viaembark demoorembark new) the copieddot.gitignore(within the template instance) is renamed to.gitignore.