Make semantic-release an option

[macklinu]

This generator is pretty specific to my personal workflow, so it might be nice to make semantic-release integration an option.

As part of this option, though, it would be cool that once all dependencies are installed, the generator will cd into the newly created directory and run semantic-release-cli setup as the final step.

[danpalmer]

Hi, +1 for this. I've just tried to set up a new project and am pretty confused right now. I'll probably end up deleting all the git commit tooling and auto-release stuff because I have Sublime set up to do my commits, and it seems the special commit wording is needed for the auto release?

[julon]

Hi @macklinu, for that you would just need to remove the .travis.yml and semantic-release from package.json since they are created/overwritten by the cli anyway? I would not remove conventional-changelog though, since the whole point is to automate the maximum by enforcing semantic-release ? (changelog generation, github release, npm deploy, etc)

[macklinu]

I'm not sure this tool should force developers to release with semantic-release. Perhaps there could be a yes/no prompt "Would you like to setup semantic-release?". If yes, add the semantic-release dependencies, set up commit message validation (using conventional-changelog), and run semantic-release-cli setup as the final step. Otherwise, leave all of that stuff out (which I think would have been caused less confusion in your experience, @danpalmer 👍 ).

Thoughts on this?