-
Notifications
You must be signed in to change notification settings - Fork 9
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
Unexpected Artifacts #3
Comments
I'd ideally not want to tinker with the repo after it is brought in. I'd suggest the README.md be any worthwhile information about the skeleton that a user might want to know. Or an empty placeholder. Should .npmignore be .gitignore? I am removing the .git repo, or at least attempting to. It gets pulled out on my machine. Again some sort of windows funk. This may be related to #2. |
…t clone of registry) in a temp holding folder before moving it to destination. Allows for easy filtering, and allows for moving of contents to current directory
Closing this out as it is encompassed by #6. |
After the skeleton was created, there were a few artifacts in the directory that I didn't expect:
I could easily remove the first two from my skeleton repo, but what about number 3?
The text was updated successfully, but these errors were encountered: