Open timwright12 opened 6 years ago
@timwright12 while this functionality sounds awesome, I am struggling to see the benefit. If our intention is to align the starting base of plugins and themes, does it make sense for themes or plugins to exist as alternate code bases on different branches. In my experience, this can get messy fairly quickly.
What is the use case/benefit you are envisioning?
@kopepasah I think it was a feature request from a while ago. Like an instance where someone wants the starter theme, but using Webpack instead of Gulp + Webpack
I could also see this as someone pulling a beta version of a release they want to was for some reason.
@timwright12 I do like the idea of customization of what is being created and think #18 could handle those types of commands. I also see the need to pull beta versions, but in that case I think it is more reasonable for someone wanting to use a beta to just clone the theme or plugin scaffold separately.
My reason for this thinking is that managing complexity of separate branches can get pretty ugly. If a branch is going to stray (and stay) far from master, then it probably should be a separate repo.
Example:
create-10up theme:feature/specific-branch-name human-project-name