Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gitignore turns into .npmignore after running grunt-init #58

Open
redonkulus opened this issue Sep 7, 2013 · 3 comments
Open

gitignore turns into .npmignore after running grunt-init #58

redonkulus opened this issue Sep 7, 2013 · 3 comments

Comments

@redonkulus
Copy link

I have a template that contains a .gitignore in the root/ folder. After I run the grunt-init scaffolding, this file turns into a .npmignore file. Is this done intentionally? Possibly a way to turn this off?

Otherwise, I guess I will have to run script to rename it back.

@ghost
Copy link

ghost commented May 3, 2014

Hello, are you there? Same for me.

@jamesplease
Copy link
Member

Which template are you guys using @Herby & @redonkulus?

@ghost
Copy link

ghost commented May 3, 2014

I have already found the reason. I (and @redonkulus, probably) use our own templates and publish them in npm. npm publish rewrites all .gitignore files into .npmignore files. When getting the package back from npm. the file is thus named .npmignore..

So, this should probably be in the entry in some FAQ: If you have template with .gitignore and upload it to npm, rename the file to, say, gitgnore-file and add a rule to rename.json.

James Smith wrote:

Which template are you guys using @Herby https://github.com/herby &
@redonkulus https://github.com/redonkulus?


Reply to this email directly or view it on GitHub
#58 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants