Skip cloning.

[mattcollier]

The use case is that there are artifact that need to be put into the npm package that are not created by any build script that is defined in the package.json file. Those artifacts also are not checked into the github repository. Therefore, if the repository is cloned, those files are absent and will not be included in the npm tarball.

I propose that we add another flag for --skip-clone that will replaces the fake conditional i've added here on L270.

[dmitrizagidulin]

+1, seems like a good addition. @mattcollier - what was the original usecase for cloning, anyways?

[dlongley]

Definitely want this behind a flag. If there's a concern that something would go wrong without the flag -- perhaps we can detect something in those cases and prevent the publication from happening (and suggest that the user might need to set that flag). I imagine some bad things could happen if we move forward without the flag, potentially including some local secrets or cruft in published npm packages. This is just my initial reaction without putting much thought into it.