This PR adds --clear option for starter-kit:export command.
We talked about whether or not to make this the default behaviour, but it gets complicated for various reasons...
Say you intentionally have .github directory in your starter kit repo, but also different .github directory in your sandbox/demo app repo, you wouldn't want to add this to your export_paths, but you also wouldn't want --clear to clear this stuff.
Or maybe you want to make changes to the stubbed composer.json, should --clear also clear that file?
etc.
We could find ways to make this behaviour more magical, but we opted to go with a simple opt-in --clear option.
When explicitly exporting with this option, the starter kit dev knows that it's going to clear everything out first, and then they can discard whatever overzealously cleared git changes they don't want before commiting 👍
This PR adds
--clearoption forstarter-kit:exportcommand.We talked about whether or not to make this the default behaviour, but it gets complicated for various reasons...
Say you intentionally have
.githubdirectory in your starter kit repo, but also different.githubdirectory in your sandbox/demo app repo, you wouldn't want to add this to yourexport_paths, but you also wouldn't want--clearto clear this stuff.Or maybe you want to make changes to the stubbed composer.json, should
--clearalso clear that file?etc.
We could find ways to make this behaviour more magical, but we opted to go with a simple opt-in
--clearoption.When explicitly exporting with this option, the starter kit dev knows that it's going to clear everything out first, and then they can discard whatever overzealously cleared git changes they don't want before commiting 👍
It's more
--clearthis way 😎